coding-standardslisted

# Code Standards Standards for site development. Concise, precise, effective. Maximum signal, minimum noise. British English throughout—code, comments, documentation, content. ## When to Use Apply these standards when implementing new code, reviewing commits, refactoring existing code, or answering questions about project conventions. The Review Checklist at the end provides a quick reference for common issues. ## Meta-Rules Preferences yield to functional reasons—if there's genuine technical need for an alternative approach, don't block it. Deviations should be explicit and justified. This is a personal project. Make clean breaking changes freely; no deprecation warnings, no backwards compatibility concerns. Ship working software over polished infrastructure. ESLint handles mechanical enforcement. These standards cover judgment calls—decisions requiring understanding of intent, not just syntax. Earn your complexity. Every abstraction, type, comment, file, and function should justify its existence. Question whether each addition clarifies intent or reduces duplication significantly; if not, inline it or delete it. **Leave code better than you found it.** When working on a file, proactively bring nearby code up to standard. Don't just implement the requested change; strengthen the surrounding code. This incremental improvement keeps the codebase healthy. Run `npm run lint -- --fix` and `npm run check` liberally. ## Architectural Philosophy Minimal friction is the