disciplined-coding

Preventing gold-plating requires enforcing strict scope discipline to limit modifications to the requested task. You can mandate reading files before editing, avoiding speculative abstractions and unsolicited refactoring during bug fixes.

Code safety is ensured by classifying actions by reversibility and requiring user approval for destructive steps. You should grep files before editing to understand context and apply minimal validation at system boundaries.

To stop unsolicited refactoring, enforce a scope discipline policy that limits modifications strictly to the requested task. This prevents speculative abstractions and extra cleanup that introduce risk during feature additions.

Use a disciplined coding approach during feature additions, bug fixes, or any code alteration requiring focused implementation. It keeps changes tight, safe, and well-documented by respecting language conventions and limiting comments.

A minimal comment policy encourages no comments unless the reasoning is non-obvious. This keeps code changes focused, avoids clutter, and ensures modifications remain strictly scoped to the requested task without unsolicited refactoring.

Yes, grepping and reading files before editing is required to ensure token-efficient navigation and maintain code safety. It verifies context, respects language conventions, and prevents destructive actions before making changes.