> For the complete documentation index, see [llms.txt](https://manual.minimal.audio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.minimal.audio/rift-manual/presets.md).
# Presets
### Overview
Rift includes over 400 presets, each exploring a different style or use case. Browse and filter with descriptive **Tags** to find exactly what you need, and mark **Favorites** so your go-to sounds are always within reach.
***
### 1. Preset Browser
Click the preset name in the center of Rift’s **Top Bar** to open the [**Preset Browser**](https://manual.minimal.audio/rift-manual/pages/AEOj8vGg9suclC5KNpJJ#id-1.-preset-browser). This view provides access to the included preset library, user presets, and future expansion packs.
Two ways to browse are available: the **Packs** tab displays themed **Packs** for different use cases, while the **Tags** tab filters all presets at once based on descriptive tags.
### 2. Preset Save View
Click the save icon on the right side of Rift’s **Top Bar** to open the [**Preset Save View**.](#id-2.-preset-save-view) This view provides essential preset-saving functionality, including the ability to add tags to your presets, making it easy to manage and organize your sounds.
---
# 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://manual.minimal.audio/rift-manual/presets.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.
