clean-code

Clean code standards are enforced by applying principles like SRP, DRY, KISS, and YAGNI to ensure efficient, maintainable code. This Skill provides specific naming rules, function rules, and structural patterns to guide development and verify code quality before file edits.

Checking dependencies before modifying a codebase involves verifying imports, tests, and shared components. Running pre-edit checks ensures proper handling of structural relationships, preventing broken dependencies and maintaining code quality during file modifications.

The Boy Scout rule applies to code structure by ensuring developers leave code cleaner than they found it. It works alongside anti-pattern checks and naming rules to enforce coding standards, resulting in maintainable and efficient codebases over time.

Yes, these coding standards guidelines include specific AI coding style guidance. They enforce pragmatic programming principles and structural patterns, ensuring AI-assisted code adheres to quality rules like DRY, KISS, and Single Responsibility.

Code breaks when editing files without checking shared components because dependencies and imports become misaligned. Performing verification checks before edits prevents breaking these dependencies, ensuring clean code and maintaining structural integrity.

The best way to prevent anti-patterns in function design is to apply strict function rules and the Single Responsibility principle. Verifying code structure against established coding standards ensures functions remain simple, maintainable, and free of redundant logic.