code-standardslisted

# Code Standards House standards for code and the artifacts around it. Apply them while writing; check them while reviewing. Where a standard has a canonical case (the specimen that set the rule), it is stated inline or in the standard's `references/` file: the concrete case recalls better than the rule. The `references/` file named under each standard carries the full detail: the why, the how-to-apply list, and the boundaries and exceptions. ## The Standards ### Fix the class, not the instance A systemic problem gets a root fix that makes recurrence impossible, never only a fix of the case at hand: the `/never-twice` skill owns this rule and its response ladder; specimen and full detail in `references/design.md`. ### Guard recurring problems with tests A problem that recurs, or plausibly will, ships with a test, tripwire, or pipeline fix that catches it at the source: rung 2 of the `/never-twice` ladder; full detail, including the guard-outside-your-reach case, in `references/design.md`. ### General-purpose over special-case Parameterize the axis that keeps changing instead of hardcoding today's instance. Specimen: a safety classifier whose rulebook kept changing was built as a classifier FACTORY with the rubric as an input. Any rubric change produces a new classifier for free, and the same machinery serves uses beyond safety. Full detail, including the one-pipeline-per-concept rule (the page that grew three visibly diverging error-band renderers) and where DRY st