> 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/set-up-template-basics-and-purpose.md).

# Set up template basics and purpose

Tell Decky when the Template should be used and what it should accomplish.

<figure><img src="https://558651701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3Qz33TugJFhuCkpYl2x%2Fuploads%2F2Cn0CgpM7mlTqHhmRhj5%2F%7B8231E874-D21B-4E4A-8A03-F91B487D948C%7D.png?alt=media&amp;token=97d6b7c2-93ec-42bc-bfd0-e947d320a064" alt=""><figcaption></figcaption></figure>

### Basics

The **Basics** step provides context about the Template. You can add:

* **Template name:** A recognizable name for the repeatable presentation.
* **Team:** The organization team or teams associated with the Template, when applicable.
* **Category:** The type or stage of presentation the Template supports.
* **Use case:** When someone should use this Template.
* **Audience:** Who the presentation is typically intended for.

<figure><img src="https://558651701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3Qz33TugJFhuCkpYl2x%2Fuploads%2FX1YBCG16IInL78UI7PYj%2F%7B19E07CBC-EF48-43DC-A923-C998361EDC57%7D.png?alt=media&amp;token=fab7ec36-5755-4d93-8d6e-1929b1cad1be" alt=""><figcaption></figcaption></figure>

### Purpose

The **Purpose** step tells Decky what the presentation should accomplish.

* **Goal:** The outcome the presentation should help drive.
* **Prompt:** Optional instructions Decky inherits whenever it creates a presentation from this Template.

Use the Prompt for recurring guidance, such as voice, writing style, important rules, or other instructions.

For example:

* **Goal:** “Prepare the customer for an executive business review.”
* **Prompt:** “Keep the presentation concise and emphasize measurable business outcomes.”

<figure><img src="https://558651701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3Qz33TugJFhuCkpYl2x%2Fuploads%2FNzgSAiVTUFX46gvDYg1V%2F%7B4B8FB78A-3645-4829-881B-4DDF57332520%7D.png?alt=media&amp;token=d2884aa3-ad7f-4efa-b5bd-cffcb09ddac9" alt=""><figcaption></figcaption></figure>

### Related articles

* [Create a template](/decky-docs/templates/create-a-template.md)
* [Add questions and file inputs](/decky-docs/templates/add-questions-and-file-inputs.md)
* [Control what Decky can change](/decky-docs/templates/control-what-decky-can-change.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/set-up-template-basics-and-purpose.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.