# Coding agent setup

> Point Claude Code, Cursor, Codex or any coding agent at MorphScreen's docs, written for agents to read.

Every page of these docs is also plain Markdown, and the whole set is one file. Give your coding agent either, and it can write MorphScreen code from the real reference instead of guessing.

## The docs, for agents

| What | Where |
|---|---|
| An index of every page, with links | [morphscreen.com/llms.txt](/llms.txt) |
| Every page in one file | [morphscreen.com/llms-full.txt](/llms-full.txt) |
| One page | its address with `.md` added, like [/docs/quickstart.md](/docs/quickstart.md) |

Every page also has **Copy Markdown** under its title, for pasting into a chat.

## A rule for your project

Add this to your agent's instructions file (`CLAUDE.md`, `AGENTS.md`, `.cursor/rules`):

```markdown
## MorphScreen

This app draws model answers with MorphScreen (@morphscreen/web).
- Docs: https://morphscreen.com/llms.txt (read the page you need as .md).
- Keep the MorphScreen key on the server; the page talks to our own route.
- Components and their attributes: https://morphscreen.com/docs/components.md
- Never render model text as HTML yourself; the SDK or /v1/render draws it.
```

## Asking for UI

The model your app uses is told about the components by the system prompt the API builds. Your coding agent doesn't need to know them to build the app, only to write [your own components](/docs/format/custom-components) or to check an answer by hand.