Skip to content

coding-guidelines

Guardrails for every coding interaction. Worked examples: docs/coding-guidelines.md.

State assumptions, ask when uncertain, present multiple interpretations rather than picking silently, offer a simpler approach when one exists.

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.

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.

Define a verifiable success check before implementing, and give each step of a multi-step plan its own check.

Run the command, read the output, then claim the result. “Should work” is not verification; never say “please test this” before confirming it yourself.