> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/creative-library/samples.md).
# Samples
Discover and use community-created editable samples.
Creative Library Samples are editable vocal/instrument clips created by the community, designed to streamline the process of music production. Each sample is a MIDI clip that includes lyrics, melody, and AI parameters.
## Browse Samples
* Click the Creative Library icon on the Toolbar at the bottom of the window to open the Creative Library panel. Navigate to the Sample Clips tab in the Creative Library panel.
* By default, all community-made samples are displayed, sorted by the community list order. Click the sample picture to preview the sample sound.
* Use the Search bar to enter search mode and filter samples based on various criteria, including genre, duration, key, language, and BPM.
* Click on My Collection to view only the samples you’ve collected.
## Collect Samples
* Uncollected samples are marked with a + icon. Click + to add the sample to your collection.
* Collected but not downloaded samples are marked with a Download button. Click the button to download the sample.
* You can drag collected and downloaded samples directly into your project or click them to use.
---
# 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://docs.acestudio.ai/creative-library/samples.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.
