> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-sections/save-to-favourites.md).
# Save to Favourites
Save time and maintain consistency by saving your frequently used section headers
### Why should I save to Favourites?
Saving to favourites gives you the flexibility to store and reuse your preferred combination of headers, descriptions, summary style and custom instructions for any conversation.
Instead of recreating these configurations each time, you can favourite (star) them for future sessions.
### Finding and Favouriting your Section Headers
Find all your recent templates under `Recently Used`
To move a template to `Favourites`
1. Click the star icon next to any configuration you want to keep
2. Double-click the configuration's title or click on \[...] to rename it
Once saved, you can access them any time from the Favourites section.
---
# 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://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-sections/save-to-favourites.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.
