> 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/quality-library/how/in-depth/custom-styling/heading-pane.md).
# Heading pane
In the Headings pane, you can map ClauseBuddy's nine levels of "Heading x" and "Heading x Title" styles to your own style.
* You can **add** a new level by clicking on the green "+ Add level" button.
* You can **delete** the last level by clicking on the trash can icon at the right/
* Many different house styles will always have a style that looks like a title on the top level (i.e., they don't allow plain heading styles at that top level). If such is the case then, check the *"Only titles on the first level"* option: it will only allow clauses with titles at the first level, and will force clauses without a title to use the style at the second level (Heading 2 in the screenshot).
When you click on the "..." button at the right, you can show additional options for ach level
* For each level, you can optionally assign a different MS Word style name for the title style. (If such separate title style name is missing, then the same MS Word style will be used for headings and heading titles on that level.)
* For each level, you can assign up to nine different MS Word styles for body paragraphs (bulleted or not) below that level. If no such separate body styles are assigned, then ClauseBuddy will use the general MS Word styles for body paragraphs that are assigned in the Body text pane discussed below.
---
# 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/quality-library/how/in-depth/custom-styling/heading-pane.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.
