clean-code

To enforce clean code standards, instruct the AI to follow pragmatic conventions like SRP, DRY, and KISS. This ensures generated feature implementations remain readable, maintainable, and free of unnecessary complexity during day-to-day coding tasks.

Maintainable code requires intention-revealing names, verb+ noun function naming, and question-form booleans. These pragmatic naming conventions clarify purpose, improve readability, and keep software changes easy to understand during future refactoring.

To prevent broken imports during refactoring, apply dependency-aware editing practices. Mandate thinking about dependencies before modifying files, and update all dependent components in the same task to ensure change-safety across the codebase.

The Boy Scout rule improves software maintainability by enforcing pragmatic standards that keep code clean during bug fixes. It directs fixing bugs immediately and leaving the codebase clearer than found, preventing overcomplicated changes over time.

Pragmatic standards are needed for code review when evaluating readability and dependency safety. Applying SRP, DRY, KISS, and YAGNI conventions ensures changes remain small, low-branch functions are used, and unnecessary complexity is avoided.

Clean code conventions require small, one-thing functions with low branching, which may limit rapid prototyping. However, these constraints enforce intention-revealing naming and change-safety discipline, ensuring long-term maintainability over quick, messy implementations.