> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/admin/write-and-rewrite.md).
# Write & Rewrite
In the Write & Rewrite settings panel, you can configure which redrafting suggestions ("prompts") must be shown towards end-users that start to redraft content.
Depending on what you select, this is what end-users will see at the bottom of their Redraft panel:
You can choose prompts from three different levels:
* The **system-level default** ("ClauseBase defaults"). The contents of those prompts are not configurable as such, although you can change the internal ordering.
* The **customer level**. This allows you to specify prompts for all your groups/departments at once.
* The **group level**. This allows you to specify prompts for one or more individual groups/departments.
Within each of those levels, you can add translations to each rule and configure the internal ordering of the rules through dragging & dropping.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.clausebuddy.com/admin/write-and-rewrite.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
