> 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/templates/control-what-decky-can-change.md).
# Control what Decky can change
Choose which parts of each slide Decky can customize and which should stay fixed.
The **Structure** step shows slides from the source presentation. Review each slide and choose how Decky should treat it.
### Locked
Use **Locked** when the slide should remain preserved. This works well for content that must stay consistent.
### Slotted
Use **Slotted** when the slide layout should remain, but selected areas can change. Decky identifies content slots within the slide.
Each slot can be:
* **Fillable:** Decky can populate or customize the content.
* **Static:** Decky preserves the content from the Template.
Slotted slides preserve a predefined layout while allowing Decky to fill designated content. This keeps fixed brand elements and layouts while customizing designated headlines, text, or other content.
### Dynamic
Use **Dynamic** when Decky should generate the slide content more freely. It does not simply fill predefined slots.
### Owner instructions
You can add optional instructions for an individual slide. These instructions guide how Decky fills or uses that slide.
For example: “Lead with the customer's most important metric and keep this section to three bullets.”
### Structure controls
The Structure area also provides controls for locking or unlocking content across slides.
### Related articles
* [What is a template?](/decky-docs/templates/what-is-a-template.md)
* [Add a dynamic slide](/decky-docs/templates/add-a-dynamic-slide.md)
* [Add questions and file inputs](/decky-docs/templates/add-questions-and-file-inputs.md)
* [Review and publish a template](/decky-docs/templates/review-and-publish-a-template.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/templates/control-what-decky-can-change.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.
