clean-code

Clean code refactoring enforces pragmatic standards like SRP, DRY, KISS, and YAGNI to improve naming, function structure, and maintainability. It focuses on intent-revealing names, small functions, guard clauses, and minimal comments to reduce bugs and rework.

Guard clauses are early returns in function design that prevent deep nesting and minimize side effects. Clean code standards enforce using guard clauses alongside limited arguments and small functions to keep code readable and reduce unintended side effects.

Clean code conventions apply directly to feature implementations and bug fixes across typical app codebases. They direct the AI to implement changes immediately, avoid over-engineering, and follow an edit-safety checklist to update dependent files and tests consistently.

Enforcing coding standards like DRY and KISS requires applying the Boy Scout rule to keep code evolving safely. It involves checking imports, dependencies, and test impact before changing any file, ensuring low coupling and clarity across the codebase.

Clean code minimizes comments to prioritize intent-revealing names and self-documenting function structure over explanatory text. It directs the AI to implement features concisely without over-explaining, asking for clarification only when requirements are unclear.