domains / families / software-engineering / uncle-bob-craft

uncle-bob-craft

authentic

Use when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.

When to use

• **Code review**: Apply Dependency Rule, boundaries, SOLID, and smell heuristics; suggest concrete refactors.
• **Refactoring**: Decide what to extract, where to draw boundaries, and whether a design pattern is justified.
• **Architecture discussion**: Check layer boundaries, dependency direction, and separation of concerns.
• **Design patterns**: Assess correct use vs cargo-cult or overuse before introducing a pattern.
• **Estimation and professionalism**: Apply Clean Coder ideas (saying no, sustainable pace, three-point estimates).
• **Agile practices**: Reference Clean Agile (Iron Cross, TDD, refactoring, pair programming) when discussing process.
• **Do not use** to replace or override the project's linter, formatter, or automated tests.

When not to use

• **Does not replace the project linter or formatter.** Run lint and format separately; this skill gives design and craft criteria only.
• **Does not replace automated tests.** It can remind you to write tests (Clean Coder, Clean Agile) but does not run or generate them.
• **Complementary to tooling.** Use it alongside existing CI, lint, and test suites.
• **No syntax or style enforcement.** It focuses on structure, dependencies, smells, and professional practice, not on brace style or line length.
• **Summaries, not the books.** Full Clean Code heuristics, component principles (REP/CCP/CRP, ADP/SDP/SAP), and detailed stories are in the books; we reference the most used parts. See [reference.md](./reference.md) "Scope and attribution."

Skill page

Source