> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/files/how-to-files/how-to-name-your-files.md). # Naming your files Naming files may seem straightforward, but there are some useful tips to take into account to make sure that the title of a file accurately represents its content and is usable for other users. ## Concepts * **Don’t start file names with a capital letter.** When you start typing the concept in a clause, you will want ClauseBase to instantly recognize it based on its name. To facilitate this, write your concepts in all lowercase. * **Uses dashes (“-“) instead of spaces between words.** Same reason as above, this makes it easier for ClauseBase to find the concept when you are using it, saving you the trouble of manually linking to it. For example, use: “data-breach” as a concept file name instead of “data breach”. --- # 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://help.clause9.com/files/how-to-files/how-to-name-your-files.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.