01 / Behavioral framing
Require evidence for claims about the codebase
A claimed function, behavior, or convention needs a file and line, an excerpt, or a reproducible command. When that evidence is unavailable, the response must say so instead of filling the gap with remembered behavior.
Source excerpt starting at line 12.12- Do not claim a Biome function, module, behavior, or convention exists without an exact file and line, a source excerpt, or a reproducible command.
02 / Behavioral framing
Keep review independent of implementation
The final review follows implementation and verification, using a fresh subagent when available. Its input contains the scope and business requirements while withholding suspected defects and expected outcomes.
Source excerpt starting at line 49.49- Provide only the review scope and intended business requirements. Do not include suspected defects, implementation hints, prior findings, or expected outcomes.
03 / Generated file guards
Map grammar edits to their generators
The file names the artifacts that must accompany a grammar change. Lint-rule and assist renames have a separate generator pair, while some full analyzer outputs can be left to CI.
Source excerpt starting at line 34.34If you change an `.ungram` file, run:35- `just gen-grammar <lang>`36- `just gen-formatter --allow-dirty`
04 / Contribution etiquette
Reserve contributor prose for the contributor
Writing code and opening a PR from supplied text have different boundaries. The agent must preserve the template and disclose assistance, but the contributor authors the description and other communication.
Source excerpt starting at line 61.61- Do not write PR descriptions or contributor communication. `CONTRIBUTING.md` requires the contributor to author that prose.
05 / Router files
Route by the kind of artifact being edited
Review, generated tests, changesets, and comments each have a named skill. Even an incidental comment edit activates the comment guide, while the catalog defines the broader trigger boundaries.
Source excerpt starting at line 68.68Load [doc-comments](./.claude/skills/doc-comments/SKILL.md) whenever editing `//`, `///`, or `//!` comments, including comments added incidentally.