> For the complete documentation index, see [llms.txt](https://docs.nuclearplayer.com/nuclear/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuclearplayer.com/nuclear/theming/themes.md).

# Themes

Overview of theme types in Nuclear.

## Basic themes

[Basic themes](/nuclear/theming/themes-basic.md) are presets that come with Nuclear. You'll find them in Preferences > Themes as clickable buttons. They adjust the app's core colors, backgrounds, and text contrast. You can't create your own basic themes.

## Advanced themes

Advanced themes give you complete creative control through JSON files. You can customize colors, accents, fonts, corner radii, border width, and shadows. They work in both light and dark modes, and you can see your changes live as you edit. Drop your JSON files in the themes folder and pick them from the Advanced themes dropdown. See [Advanced themes](/nuclear/theming/themes-advanced.md) for details.

## Theme store

The theme store lets you browse and install community-created themes from within Nuclear. You can install them with a single click, and contribute yours. See [Theme store](/nuclear/theming/theme-store.md) for details.


---

# 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://docs.nuclearplayer.com/nuclear/theming/themes.md?ask=<question>&goal=<user_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.