> 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/writing-rules.md).

# Writing rules

Guide how Decky writes presentation content for your company.

Guide how Decky writes presentation content for your company.

### Set communication standards

Themes control more than visual design.

Writing rules tell Decky how presentation content should sound. They also guide how Decky communicates information.

Writing rules can cover:

* Tone
* Conciseness
* Terminology
* Preferred writing patterns
* Things Decky should avoid

You can ask the Theme agent to:

* “Keep headlines concise.”
* “Avoid overly promotional language.”
* “Use our preferred product terminology.”
* “Make executive slides more direct.”

Writing rules help Decky apply consistent communication standards across presentations.

### Related articles

* [Make changes to your theme](/decky-docs/brand-and-themes/make-changes-to-your-theme.md)
* [Typography](/decky-docs/brand-and-themes/typography.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/writing-rules.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.