# Docs for assistants

> How assistants read the 00 Simulator docs: a Markdown twin of every page, llms.txt, llms-full.txt, and the connector’s own docs search.

Source: https://simulator.00aud.io/docs/ai/docs-for-assistants

Every page of these docs can be read by an assistant as well as by you: as Markdown, as one index or one file, or through the connector’s own docs tools. It is the same text you read, so what your assistant quotes is what the page says.

- **Any page:** Add `.md` to its address
- **Index:** `https://simulator.00aud.io/llms.txt`
- **Everything:** `https://simulator.00aud.io/llms-full.txt`

## Every page as Markdown

Add `.md` to any docs address and you get the page as plain Markdown: `https://simulator.00aud.io/docs/reference/tiles/port-velocity.md`. The docs home as Markdown, `https://simulator.00aud.io/docs.md`, lists every page with a line on each.

- It starts with the title, a one-line summary and the page’s address, then the page itself.
- A figure becomes its description, followed by the numbers it shows as a table where it has them.
- An interactive walkthrough becomes a one-line note; prompts keep their full text.
- Links to other pages are full addresses, so they still work outside this site.

The Markdown is built from the same content as the page when the site is built, so the two cannot differ. Beside each page, Copy as Markdown copies it and View as Markdown opens it.

## llms.txt and llms-full.txt

`https://simulator.00aud.io/llms.txt` follows the [llms.txt convention](https://llmstxt.org): what 00 Simulator is, how to read the docs, then every page tab by tab with its Markdown address and a one-line description. `https://simulator.00aud.io/llms-full.txt` is every page in one file, in reading order, for pasting into a long chat or a project’s files.

```markdown
# 00 Simulator

> 00 Simulator is a loudspeaker enclosure simulator that runs in the browser. It models sealed, vented, passive-radiator, bandpass and horn enclosures from a driver’s T/S parameters, and assistants such as Claude and ChatGPT can use it through its connector.

Every docs page is also served as Markdown: add `.md` to its address, as in the links below. All of the docs in one file: https://simulator.00aud.io/llms-full.txt. Assistants connected to 00 Simulator (https://simulator.00aud.io/mcp) can search these docs and read a page or one section with the `search_docs` and `read_doc` tools.

…

## AI

- [Docs for assistants](https://simulator.00aud.io/docs/ai/docs-for-assistants.md): How assistants read the 00 Simulator docs: a Markdown twin of every page, llms.txt, llms-full.txt, and the connector’s own docs search.
…
```

## search_docs and read_doc

With 00 Simulator connected, your assistant has two docs tools, and the connector tells it to use them for how-to questions: search, read the best match, and quote the docs with a link instead of answering from memory. Both need nothing beyond signing in.

| Tool | What your assistant reads |
| --- | --- |
| `search_docs` | Search the 00 Simulator docs: how to do something in the app, and what a tile, result, setting or term means. Returns the best matching pages, sections, tiles and glossary terms, each with a url and a one-line summary. Then read the best match with `read_doc` and quote it with its url, rather than answering from memory. |
| `read_doc` | Read a 00 Simulator docs page as Markdown. Pass a url from `search_docs` or a docs path such as /docs/reference/tiles/port-velocity (/docs is an overview of every page). Pass section, a heading on the page, to read only that part; a url ending in #section reads just that section. Quote what you use and link its url. |

- Search uses the same index and ranking as the search box on this site (⌘K), so it finds the pages you would.
- `read_doc` returns the page’s Markdown twin, or just one section of it, with the address to link.

## An answer, step by step

Someone with the vented example open (the Ciare 12.00SW in 55 L, tuned to 32 Hz, one 10 cm port, at 200 W) asks their assistant: “Why does my sub chuff when I turn it up?”

1. **Search the docs.** `search_docs` for “port chuffing” finds the [Port Velocity](https://simulator.00aud.io/docs/reference/tiles/port-velocity) tile page and [Fix a noisy port](https://simulator.00aud.io/docs/guides/noisy-port).
2. **Read the design.** `get_workspace` reads the saved design: the driver, the box, the port and the power.
3. **Try a change without saving it.** `simulate_workspace` runs it as it is and again with two ports. The port’s peak air speed goes from 28.4 m/s to 14.2 m/s, and each port grows from 35.6 cm to 77.1 cm long to keep the tuning.
4. **Read the part that explains it.** `read_doc` reads the [What moves it](https://simulator.00aud.io/docs/reference/tiles/port-velocity#what-moves-it) section of Port Velocity.

> **The answer it can give** Your port peaks at **28.4 m/s** at 200 W, over the 17 m/s line where ports start to be heard. Two 10 cm ports bring it to **14.2 m/s**, but each must be 77.1 cm long to keep 32 Hz, so check it fits the box. [Port Velocity › What moves it](https://simulator.00aud.io/docs/reference/tiles/port-velocity#what-moves-it)

## Point any assistant at the docs

- Connected to 00 Simulator: just ask. It searches and reads these docs itself. See [Connect your assistant](https://simulator.00aud.io/docs/ai/connect).
- Not connected, but it can open web pages: give it a page’s address, its `.md` twin, or `https://simulator.00aud.io/llms.txt`, and ask it to read what it needs.
- No web access: use Copy as Markdown on the page and paste it into the chat, or save llms-full.txt and attach it.
- On any page, Ask your assistant writes a prompt that names the page: copy it, or open it in Claude or ChatGPT with the prompt filled in.

```
Read https://simulator.00aud.io/llms.txt, then the 00 Simulator docs pages you need, and answer from them with links: what does the Headroom tile show, and when should I worry about it?
```

## Ask your AI

**Ask your AI**

With the connector, your assistant quotes the docs instead of answering from memory.

> Using 00 Simulator, search the docs for how the Headroom tile works, read me the part that explains it, and link the page.