coding-guidelines

To reduce coding mistakes, apply formal coding guidelines that enforce thinking before coding, making surgical changes, and defining verifiable success criteria. This approach surfaces assumptions and tradeoffs before making any code modifications.

Best practices for code reviews and refactoring involve applying a conservative change strategy that touches only necessary code. This surgical approach ensures minimal, justified edits while maintaining verifiable success criteria throughout the implementation process.

Yes, these coding guidelines are applicable to bug fixes and feature development across software projects. They provide behavioral rules to reduce common LLM coding mistakes by enforcing goal-driven execution and conservative change strategies.

Defining verifiable success criteria requires establishing clear goals before execution and iterating until confirmed. This goal-driven approach ensures implementation tasks meet defined quality standards while reducing framing errors and careless mistakes.

Surfacing assumptions and tradeoffs before coding prevents subtle errors and inconsistent practices that degrade software quality. This guideline ensures developers think before coding, leading to safer, clearer development with minimal unnecessary edits.

Conservative change strategies work effectively for debugging and implementation tasks by ensuring surgical changes that touch only necessary code. This approach minimizes unnecessary edits to surrounding code while maintaining focus on verifiable success criteria.