---
name: standards
description: Use when capturing how code must be written in this project - typing strictness, library-vs-build posture, paradigm, error handling, testing style, git and commit discipline, and what an AI assistant must never do here - via an interview, producing a normative standards doc that outranks generic best practice. Binding rules you decided, not a description of what the code currently does; the observed conventions live in the reference's own conventions chapter.
---

# Capstone: standards

From this skill's base directory, read `../core/references/core.md`
and `../core/references/core-authoring.md`, then execute
`../core/references/protocols/standards.md`
exactly.