code-standardslisted

# Code Standards Language-agnostic defaults. Language-specific skills override where they conflict. These are the Chef's taste stated as directives: apply them as written, and do not substitute your own or your provider's defaults where they differ. ## Core Philosophy - **Modular**: small, focused, reusable components. - **Functional first**: pure functions, immutability, composition. A house choice, not a suggestion. - **Maintainable**: self-documenting, testable, predictable. - **Single source of truth**: one authoritative owner per fact; no drifting duplicates. - **Separate by rate of change**: don't weld a fast-changing concern into a slow-changing one; couple the layers loosely so each moves at its own pace. - **Docs are part of the system**: incorrect documentation is a bug. When a change alters docs that describe the system's behavior, verify them against the code as it stands, not just for prose. (OpenBSD.) **Golden Rule**: If you can't easily test it, refactor it. ## Laziness (the YAGNI ladder) The best code is the code you never wrote. Before writing any, stop at the first rung that holds: 1. **Does this need to exist?** Speculative need = skip it, say so in one line. 2. **Stdlib does it?** Use it. 3. **Native platform feature covers it?** (`<input type="date">` over a picker lib; a DB constraint over app code.) Use it. 4. **An already-installed dependency solves it?** Use it. Never add one for what a few lines do. 5. **One line?** One line. 6. **Only then:**