engineering-standardslisted

# Clean Code Methodology The design and implementation bar for the planner, implementer, and code-reviewer. ## Core Philosophy Six lenses, applied as severity guidance when a decision is contested: - **Hickey** — simple, immutable data and pure functions. - **Carmack** — implement directly; keep a way to measure performance. - **Armstrong** — isolate failures so one module's fault does not propagate. - **Knuth** — clarity before cleverness. - **Liskov** — honor interface contracts (`skills/solid/SKILL.md` carries LSP and SRP in full). - **Ousterhout** — deep modules, simple interfaces; pull complexity downward. **Cost-benefit, not religion.** Every test, abstraction, and interface has an ongoing cost: maintenance, runtime, false-positive triage, cognitive load. A test that catches no real bug and slows the build is a liability. Premature DRY couples behaviors that need to evolve independently. Apply the **Rule of Three**: tolerate duplication the second time, extract on the third. ## Code Comments These rules govern comments inside source files, not review findings, which use `skills/conventional-comments/SKILL.md`. Comments never explain WHAT the code does. Intention-revealing names and structure carry that. A comment is permitted only for a non-obvious WHY, such as a constraint, a workaround, or a surprising requirement, and only when neither intention-revealing code nor tests can carry the explanation. - **Rewrite first.** A comment that feels necessary is a sig