# For AI agents

> Machine-readable docs: llms.txt, Markdown twins, tokens and types.

## Read the system as a model

- **[llms.txt](/design/llms.txt)** lists every page with a one-line summary, in the llms.txt format.
- **[llms-full.txt](/design/llms-full.txt)** is the whole site in one Markdown document.
- **[manifest.json](/design/manifest.json)** is the catalogue: pages, guides, components (name, group, product, summary, source, import, preview and Markdown URLs), agents, themes and files.
- **[tokens.json](/design/tokens.json)**, **[tokens.dtcg.json](/design/tokens/tokens.dtcg.json)** and **[index.d.ts](/design/lib/index.d.ts)** carry exact values and types.

## Markdown twins

Every page has a Markdown twin at the same path plus `.md`: `/design/components/button.md`, `/design/foundations/colour.md`; the overview is `/design/index.md`. Each HTML page links its twin with `<link rel="alternate" type="text/markdown">`.

A component page in Markdown always has the same parts: a one-line summary, **Facts** (group, product, source, import), **Guidelines** (use, props, anatomy with exact values, behaviour, don'ts), **API** (TypeScript declarations) and **Example** (runnable code).

## Give it to your agent

```text
Use the Digital Crew design system: https://www.digitalcrew.tech/design/llms.txt
Read the overview and the story first. Before generating UI, read the page of each
component you use. Use token names (never raw values), the theme of the product
(crew-* or max-*), sentence case in product UI, and one colour per agent.
```
