clean-code

To refactor code for maintainability, enforce pragmatic coding standards like SRP, DRY, KISS, and YAGNI. This involves standardizing naming conventions, optimizing functions to be small and focused, and promoting flat code structures with guard clauses.

Core clean code principles include SOLID, DRY, KISS, and YAGNI. They enforce conciseness, clarity, and maintainability by requiring clear naming conventions, small functions with minimal arguments, and flat code structures to avoid unnecessary complexity.

Apply coding standards during generation and modification by performing pre-edit checks to assess dependencies and impact. Follow AI coding style guidelines, use guard clauses, and run mandatory script verifications post-completion to ensure all tests pass.

Yes, these pragmatic coding standards are language-agnostic. They focus on universal software engineering principles like Single Responsibility, clear naming conventions, and small focused functions, ensuring maintainability across all code generation and modification tasks.

The best way to structure functions for clean code is to keep them small and focused with minimal arguments. Promote a flat code structure by using guard clauses to handle edge cases early, and favor composition over deep nesting for maintainability.

Refactored code may fail tests if pre-edit dependency checks or post-completion self-checks were skipped. You must run mandatory script verifications after modifications to ensure all requirements are met, the code works, and tests pass.