coding-guidelines

Prevent coding errors during feature implementation by establishing explicit assumptions, clarifying ambiguity, and defining verification criteria before coding. Maintain focused code modifications and avoid unnecessary refactors to ensure safer software changes.

Approach refactoring safely by enforcing minimal scope changes and surgical edits. Avoid unrelated cleanup and speculative features, ensuring disciplined reasoning and goal-driven verification criteria to preserve existing software functionality during code modifications.

Keep code modifications focused during bug fixes by avoiding unnecessary refactors and speculative features. Define verification criteria upfront, apply surgical edits, and maintain minimal scope changes to ensure the bug fix does not introduce new coding errors.

Yes, you need to define verification criteria before starting implementation. Goal-driven development requires establishing these criteria upfront to guide deliberate software changes, verify implementation success, and prevent common LLM coding mistakes during code modifications.

Adding speculative features causes bugs because it expands the scope of code modifications beyond the original implementation goal. Unnecessary refactors and unrelated cleanup introduce untested changes, bypassing the disciplined reasoning needed for safer software changes.

You should not use minimal scope changes when a task explicitly requires broad architectural updates or large-scale refactoring. This approach focuses on surgical edits and cautious implementation, making it unsuitable for scenarios needing extensive, sweeping code modifications.