clean-code

To enforce clean code standards and prevent over-engineering, apply pragmatic coding rules like KISS and YAGNI. This ensures AI agents write concise, direct, and solution-focused code without unnecessary complexity.

The best way to refactor code for the Single Responsibility Principle is to optimize function design. Create small, focused functions with minimal arguments, no side effects, and clear, intent-revealing naming conventions.

The Boy Scout Rule applies to refactoring by mandating that you leave code cleaner than you found it. It promotes continuous improvement through guard clauses, flat nesting, and removing anti-patterns during routine edits.

Yes, you can automate linting and type coverage checks by running mandatory verification scripts. Pre-completion checklists ensure code meets quality standards, structure patterns, and internationalization requirements before finalizing.

Common anti-patterns include deep nesting, side effects, and poor naming. Fix them by applying DRY and KISS principles, using guard clauses, standardizing naming conventions, and creating focused functions to reduce complexity.

You need to apply these coding standards whenever you write or modify code to ensure maintainability. Defining AI coding styles and running pre-editing self-checks guarantees consistent quality and prevents unnecessary complexity.