AI agents

Give your agent the rules

Save the agent guide into your project. It tells the agent where Lathe's index lives, how to install items, which assembly to start from for each kind of page, and the conventions every component follows.

# Claude Code, Codex and most agents read AGENTS.md
curl -o AGENTS.md https://latheui.dev/agents.md

# Cursor
mkdir -p .cursor/rules && curl -o .cursor/rules/lathe.mdc https://latheui.dev/agents.md

Already have an AGENTS.md or CLAUDE.md? Append the file to it instead, or add one line: Read https://latheui.dev/agents.md before building UI.

Readable indexes

• llms.txt lists every component with a one-line description, its page and, for free items, its registry source.
• llms-full.txt has every component's usage, props, keyboard and accessibility notes in one file, for agents that read a whole context at once.
• agents.md is the guide above.

Browse and install over MCP

With the shadcn MCP server, an agent can search the registry and install items itself. Setup takes one command; the MCP guide has the details.

pnpm dlx shadcn@latest mcp init --client claude

Prompts on every page

Each component and assembly page ends its usage section with a prompt you can paste into your agent. It names the item, the install command and the page to read, so the agent works from the documentation rather than from memory. For example: