llms.txt and Markdown pages
Every page on this site also exists as plain Markdown, and two files at the root list or contain all of them. Use them to give a model the engine's docs without HTML: paste a page into a chat, add the index to an agent's context, or download everything once.
| URL | What it is | Use it when |
|---|---|---|
https://docs.moonspell.app/llms.txt | The index, in the llms.txt format: a # Moonspell heading, a short summary in a blockquote, then one ## section per sidebar category with a link and a one-line description for each page, in sidebar order. | An agent should find the right page itself. Small enough to keep in context. |
https://docs.moonspell.app/llms-full.txt | Every page's Markdown in sidebar order, each one starting with # <title> and Source: <url>. | You want the whole manual in one file, for a long-context model or a local copy. |
https://docs.moonspell.app/<path>.md | The Markdown of one page: front matter removed, the title as the first heading. The path is the page's URL path. | You need one topic, for example https://docs.moonspell.app/engine/audio.md or https://docs.moonspell.app/backend/realtime.md. |
The files are built from the same Markdown sources as the site, so they change when the site does.
What llms.txt looks like
Each section is a sidebar category; each line is a page's title, its .md URL and its description. The "Build with AI" section starts like this:
## Build with AI
- [Build with AI](https://docs.moonspell.app/ai/overview.md): What a coding agent gets from a Moonspell game repo (CLAUDE.md, AGENTS.md, 24 skills, agent docs, examples, GDD.md and playtest.json) and why the engine is shaped for agents.
- [Claude Code and other agents](https://docs.moonspell.app/ai/claude-code.md): Step by step, open a Moonspell game repo in Claude Code or another coding agent, ask for a game, let the agent check its own work, and know which skills assume the hosted Moonspell app.
Read them from a terminal
# The index
curl -s https://docs.moonspell.app/llms.txt
# One page as Markdown
curl -s https://docs.moonspell.app/engine/audio.md
# Everything, saved next to your game
curl -s -o moonspell-docs.txt https://docs.moonspell.app/llms-full.txt
Paste into a chat
For a question about one engine piece, open its .md URL in a browser, copy the text and paste it into the chat with your question. For a broad question ("which module fits a farming game?"), paste llms.txt and ask the model to say which pages it needs; then paste those.
Add them to an agent's context
A game repo already carries the template's own docs in docs/ and the skills in .claude/skills/. These site docs add the explanations and the backend and platform pages. Two ways to give them to an agent:
Point to the index. Add a line to a project file the agent reads, such as the end of CLAUDE.md or AGENTS.md, and the agent fetches what it needs:
## Engine docs
The Moonspell engine's docs are at https://docs.moonspell.app/llms.txt (an index).
Every page there is also Markdown: add .md to its URL.
Read the page for an engine piece before changing how the game uses it.
This needs an agent that can fetch URLs.
Keep a local copy. Download llms-full.txt into the repo and import it. In Claude Code, an @path line in CLAUDE.md loads the file into context at the start of every session:
curl -s -o docs/moonspell-docs.txt https://docs.moonspell.app/llms-full.txt
echo "@docs/moonspell-docs.txt" >> CLAUDE.md
The full file is large, so this uses a lot of context in every session. Importing a few single pages, saved the same way from their .md URLs, is often enough.
For search instead of whole files, connect the docs MCP server.