> For the complete documentation index, see [llms.txt](https://docs.studio.uzu-app.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.studio.uzu-app.com/en/scenariohome/overview/sub.md).
# Setting sub-images
In addition to the key visual, you can set up to 10 sub-images for your cover.
Please follow the rules below when setting sub-images:
* The key visual must always be set as the top image, not as a sub-image.
* Do not upload content that violates public morals or decency.
{% hint style="info" %}
Examples of what can be used as sub-images:
* Alternative versions of the key visual
* Character introduction images
* Images introducing the scenario's theme or overview
* Introduction comics or illustrations
* Pre-play cards or screenshots that players can use
{% endhint %}
{% hint style="danger" %}
Examples of what **cannot** be used as sub-images:
* Content containing spoilers for the scenario
* Advertisements leading to external websites
* Unrelated content
* Promotions for other scenarios
{% endhint %}
---
# 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://docs.studio.uzu-app.com/en/scenariohome/overview/sub.md?ask=&goal=
```
`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.