clean-code

To enforce clean code standards during AI refactoring, apply pragmatic principles focusing on conciseness, directness, and avoiding over-engineering. This ensures refactored modules maintain readability and adhere to the Single Responsibility Principle while running automated linting checks.

To reduce technical debt, apply coding standards like SRP, DRY, KISS, and YAGNI. These principles guide naming conventions, function design, and code structure to improve maintainability, readability, and overall development velocity.

Prevent over-engineering in AI-generated code by enforcing pragmatic principles that mandate directness and conciseness. This approach guides AI agents to write simple, well-named functions and avoid unnecessary complexity during module refactoring.

Yes, this approach works for validating code quality by mandating rigorous self-checks and script executions before task completion. It ensures AI agents run automated linting and type coverage checks to validate maintainability and efficiency.

The best way to structure AI coding interactions for bug fixing is to direct agents to write code directly, fix bugs immediately, and ask for clarification only when needed. This maximizes developer efficiency and productivity.

Use SRP and DRY principles for code maintainability when refactoring complex modules to ensure the resulting code is simple, well-named, and structurally sound. This reduces technical debt and improves long-term development velocity.