# AGENTS.md Read by Grok Build, Claude Code, GitHub Copilot, Cursor and Gemini CLI. One file, every vendor's agent — which is why this is the piece of configuration worth investing in: it is not lock-in. Keep it short. It loads on every request, so a merely nice-to-have rule dilutes the ones that matter. Replace everything below with your project's facts. ## Commands Things an agent cannot guess and will otherwise invent: ``` e.g. cargo fetch / pnpm install --frozen-lockfile e.g. cargo build --workspace e.g. cargo test -p mycrate test_name e.g. cargo test --workspace e.g. cargo clippy --all-targets -- -D warnings ``` Prefer running a single test over the whole suite while iterating. ## Architecture boundaries State the rules a reasonable person would break by accident, and say *why* — a rule with a reason survives a situation you did not anticipate. - `` must not depend on ``. (Reason: …) - All outbound HTTP goes through ``. (Reason: retries and tracing.) - `` is generated from ``. Never hand-edit. ## Conventions that differ from the default Only what departs from the language or framework norm. The linter covers the rest, and repeating it wastes the budget. - … ## Known traps - … ## Where the real documentation lives - `` — the work wiki: hosts, decisions and why, runbooks, who owns what. Read it before asking me about infrastructure.