> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-do-i-change-appearance-settings.md).
# Appearance Settings
Use **Settings → Appearance** to make Stellar comfortable to read and navigate on your screen.
### Choose a theme
Under **Theme**, select Light or Dark. Choose whichever is easier for you to read.
### Change the interface size
Adjust **User Interface Scale**. Available sizes are 50%, 75%, 100%, 125%, 150%, and 200%.
* A higher percentage makes text and controls larger but fits less on screen.
* A lower percentage fits more on screen but makes text and controls smaller.
* Start at 100%, then adjust to suit your display.
### Make scrollbars easier to grab
Adjust **Scrollbar Size** separately from the interface scale. Available widths are 6px, 8px, 10px, 12px, 14px, and 16px. A larger width makes the scrollbar easier to grab with your mouse.
If controls feel too small, increase the interface scale. If only the scrollbar is difficult to use, increase its width instead.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-settings-tab/how-do-i-change-appearance-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.