constitutionlisted

# Constitution ## Core Rule Never write a principle the user hasn't seen. Each entry in `golden-principles.yaml` lands only after the user accepts the proposed `rule`, `severity`, and `detect` together — silent insertion (even of "obvious" rules) breaks the audit contract downstream. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/constitution` when: - A new project doesn't have `golden-principles.yaml` yet and you want one - An existing project has a sparse principles file and you want to fill in gaps from category recommendations - You ran `/quality-audit` and got the "no principles file found" stub — this skill is what the stub points at - Onboarding to a project and want to capture its de-facto rules as explicit, machine-checkable ones Not for: - Editing arbitrary principles (use a text editor — this skill is for *adding* and *bootstrapping*) - Running the principles against the codebase — that's `/quality-audit`'s job - Generating coding standards prose — `golden-principles.yaml` is for *deterministic, grep-checkable* rules; verbose conventions belong in `agent_docs/conventions.md` or `docs/design-docs/core-beliefs.m