# Use these docs with AI

> Give an AI assistant the Feather documentation as plain Markdown, in full or by topic, so it can answer questions and drive the engine accurately.

Source: https://feather-engine.com/docs/agents/ai-docs/

Every page of this documentation is also published as plain Markdown, and the whole site is available
in the [llms.txt](https://llmstxt.org/) format that AI tools read. Pair the docs with Feather's
[MCP server](/docs/agents/mcp/) and an assistant can both learn how a system works and make the change
for you.

## What's available

| File | Contents | Use it when |
| --- | --- | --- |
| [`/llms.txt`](/llms.txt) | A short index of the documentation and the topic files below | You want the assistant to choose what to read |
| [`/llms-full.txt`](/llms-full.txt) | Every page in one file, including the full command reference | The assistant has a large context window |
| [`/llms-small.txt`](/llms-small.txt) | Every page, with tips, notes and extra detail removed | You need the whole engine in less space |
| `/_llms-txt/<topic>.txt` | One topic: getting started, agents, world and rendering, gameplay and logic, or animation, audio, UI and shipping | You are working on one area |
| `/docs/<page>.md` | A single page, for example [`/docs/gameplay/combat.md`](/docs/gameplay/combat.md) | You need one system in detail |

Each page also has three buttons under its title:

- **Copy page for AI** copies the page as Markdown, ready to paste into a chat.
- **View as Markdown** opens the same Markdown in the browser.
- **Ask Claude** starts a Claude conversation that reads the page.

## Give your coding assistant the docs

Add a line to your project's assistant instructions so it reads the docs before working on your game.
For Claude Code, put it in `CLAUDE.md` next to your `project.feather.json`:

```markdown
## Feather Engine
This is a Feather Engine 2 game. Before changing it, read https://feather-engine.com/llms.txt
and the topic files it links to. Prefer `feather-cli catalog` over the docs if they disagree.
```

Then connect the [MCP server](/docs/agents/mcp/) so the assistant can act on what it reads.

## Docs and the live catalog

The docs explain how systems fit together, what the editor panels do and which settings matter. The
command catalog is the exact, current contract. When an assistant needs the precise arguments for a
command, it should read them from the catalog:

```bash
feather-cli catalog > catalog.json
```

MCP clients receive the same schemas automatically through tool discovery.

:::note
The documentation is regenerated as the engine changes. If you build Feather from source, your build
may be newer than the published docs; the catalog from your build is always authoritative.
:::