Code Standards

Standards for code and the artifacts around it. Apply them while writing. Check them while reviewing.

Readability and beauty come first. Every standard here serves them and yields where following it would read worse; the deviation is said in a line, never forced through.

This is a silver standard, not gold. Languages and tools move faster than this page: a newer version's more beautiful, more readable way of writing a thing wins even where the page has not caught up, and the page is brought up to it afterwards.

Each standard below is the rule in a few lines, with the specimen that set it where one exists. The references/ page named under it carries the why, the how-to-apply list, and the boundaries. Load that page before acting on a standard's edge.

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 the judgment and its response ladder. Full detail: references/design.md.

Guard what passes the floor

A problem that passes the /never-twice floor's judgment ships with the highest reachable rung: a type or structure that makes the state impossible, else a test, tripwire, or pipeline fix (or a proposal to the user when the pipeline is out of reach), else a written rule recorded as debt. Full detail: references/design.md.