# Brief the agent: the documents a build runs on

URL: https://kywi-docs-production.up.railway.app/agent/brief-the-agent-the-documents-a-build-runs-on
Type: docPage

Every generated project ships an AGENTS.md header plus the building-patterns guide verbatim, the document meant to brief an agent — CLAUDE.md just points at it.

`AGENTS.md` is the document a build actually runs on. `CLAUDE.md` exists only to send a Claude Code session there — it holds no guidance of its own beyond that pointer.

## What AGENTS.md actually contains

The file opens with a short, project-specific header: a sentence naming the deployment mode, a "Where things live" list built from what the generator finds on disk in *this* project, and the three commands that bring it up (`pnpm migrate`, `pnpm seed`, `pnpm dev`). Everything after that header is Kywi's canonical building-patterns guide, appended in full and unmodified — not a summary, not an excerpt. Reading `AGENTS.md` means reading both: the header tells an agent what's true of this project, the guide tells it what's true of Kywi.

## CLAUDE.md is three paragraphs

It says to read `AGENTS.md` first, states the core principle — model content in the CMS instead of hardcoding it — and, in its last line, names all four skills: `kywi-content-model` for anything not built yet, plus a pointer to the collections, custom-modules and personalization skills alongside it in `.claude/skills/`. That's the whole file. If you're looking for project-specific guidance and only find generic instruction to go elsewhere, you're reading the wrong one.

The header's "Where things live" bullets are assembled from what's actually on this project's disk rather than fixed boilerplate, and the version stamp at the top of `AGENTS.md` is not a freshness check — see [retrofitting an existing project](/agent/retrofit-an-existing-project-for-agents/) for both, and for how to refresh a stale copy deliberately.
