uncle-bob-craft

Check that dependencies point inward so use cases never import UI or database details, verify SOLID principles in the changed code, and list smells like rigidity or opacity. The skill provides a copy-paste checklist and suggests concrete refactors such as extracting functions or inverting dependencies.

Introduce a pattern when you hit the third duplication or a second reason to change the same module. Avoid adding Factory or Strategy to simple linear code, since that adds indirection without reducing duplication or clarifying intent.

No. It provides design and craft criteria only, covering structure, dependencies, smells, and professional practice. Syntax and style enforcement remain the responsibility of your project linter and formatter, which you should always run separately.

The clean-code skill covers the Clean Code book in detail: naming, functions, comments, and formatting. Uncle-bob-craft aggregates cross-book criteria including Clean Architecture boundaries, Clean Coder professionalism, Clean Agile practices, and design pattern discipline.

The seven core smells are rigidity, fragility, immobility, viscosity, needless complexity, needless repetition, and opacity. Each maps to a concrete fix such as reducing coupling, extracting shared logic, or renaming for clarity.