---
name: llms-txt
description: Write or fix an /llms.txt file that follows the llmstxt.org proposal. Use when a user asks for an llms.txt file, asks how to give AI agents a map of the site, or wants Markdown versions of key pages.
---

# llms.txt

## Goal
Give language models and agents a short Markdown map of the most useful pages on the site.

## Facts to use
- The proposal is at llmstxt.org. The file lives at `/llms.txt` on the site root.
- The only required part is one H1 with the name of the project or site.
- Optional next: a blockquote with a short summary.
- Then optional paragraphs or lists with details (no headings), then optional H2 sections that hold link lists.
- Each link line uses the form `- [Name](https://url): optional notes`.
- An H2 section named `Optional` holds links an agent can skip when its context is short.
- The proposal also recommends a clean Markdown copy of a page at the same URL with `.md` added (or `index.md` for a URL without a file name).
- llms.txt is a proposal, not a search engine standard. Treat the file as a low-cost aid for agents and tools, not as a ranking signal. Do not promise traffic from it.

## Workflow
1. Read the home page, the sitemap and the main navigation.
2. Pick at most 30 links: product or service pages, pricing, docs, guides, about, contact, policies.
3. Write one plain sentence of notes per link. Say what the page answers.
4. Group links under H2 sections such as `Product`, `Docs`, `Guides`, `Company`, `Optional`.
5. Use absolute URLs that return 200 and are canonical (no redirects, no tracking parameters).
6. Serve the file as `text/plain` or `text/markdown` with status 200.

## Template
```markdown
# Example Co

> Example Co makes invoicing software for small agencies.

Example Co has a free plan and two paid plans. Data is stored in the US.

## Product
- [Pricing](https://example.com/pricing): Plans, limits and prices.
- [Features](https://example.com/features): What the app does.

## Docs
- [Getting started](https://example.com/docs/start): Set up an account in five steps.

## Optional
- [Changelog](https://example.com/changelog): Release notes.
```

## Checks
- [ ] Exactly one H1, at the top.
- [ ] Every link returns 200 and is the canonical URL.
- [ ] The notes match the page content today.

## Output
Return the full file in a code block and a list of links you left out, with the reason.

## Sources
- llmstxt.org: The /llms.txt file. https://llmstxt.org/
