coding-guidelines
Coding Guidelines
Section titled “Coding Guidelines”Guardrails for every coding interaction. Worked examples: docs/coding-guidelines.md.
1. Think Before Coding
Section titled “1. Think Before Coding”State assumptions, ask when uncertain, present multiple interpretations rather than picking silently, offer a simpler approach when one exists.
2. Simplicity First (YAGNI / KISS / DRY)
Section titled “2. Simplicity First (YAGNI / KISS / DRY)”No features beyond what was asked, no single-use abstraction, no unrequested flexibility, no handling of impossible cases. If 200 lines could be 50, rewrite.
3. Surgical Changes
Section titled “3. Surgical Changes”Don’t “improve” adjacent code or refactor what isn’t broken; match existing style; remove only what YOUR changes made unused. Test: every changed line traces directly to the user’s request.
4. Goal-Driven Execution
Section titled “4. Goal-Driven Execution”Define a verifiable success check before implementing, and give each step of a multi-step plan its own check.
5. Verify Before Claiming Done
Section titled “5. Verify Before Claiming Done”Run the command, read the output, then claim the result. “Should work” is not verification; never say “please test this” before confirming it yourself.