> For the complete documentation index, see [llms.txt](https://decky.gitbook.io/decky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://decky.gitbook.io/decky-docs/brand-and-themes/imagery.md).

# Imagery

Guide the visual style of images Decky uses in presentations.

Guide the visual style of images Decky uses in presentations.

### Set the visual direction

Imagery defines the visual direction Decky follows for presentation images.

This keeps images consistent with your company’s presentation style.

> **Imagery defines the visual style Decky should follow. Brand images & assets are specific approved files Decky can reuse.**

Update Imagery when generated or selected visuals consistently feel off-brand.

You can also ask the Theme agent: “Make imagery feel more editorial and less like stock photography.”

### Related articles

* [Brand images & assets](/decky-docs/brand-and-themes/brand-images-and-assets.md)
* [Make changes to your theme](/decky-docs/brand-and-themes/make-changes-to-your-theme.md)
* [Backgrounds](/decky-docs/brand-and-themes/backgrounds.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://decky.gitbook.io/decky-docs/brand-and-themes/imagery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.