uncle-bob-craft

name	uncle-bob-craft
description	Use when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.
category	code-quality
risk	safe
source	community
date_added	2026-03-06
author	antigravity-contributors
tags	["clean-code","clean-architecture","solid","code-review","craftsmanship","uncle-bob"]
tools	["claude","cursor","gemini"]

Uncle Bob Craft

Apply Robert C. Martin (Uncle Bob) criteria for code review and production: Clean Code, Clean Architecture, The Clean Coder, Clean Agile, and design-pattern discipline. This skill is complementary to the existing @clean-code skill (which focuses on the Clean Code book) and to your project's linter/formatter—it does not replace them.

Overview

This skill aggregates principles from Uncle Bob's body of work for reviewing and writing code: naming and functions (via @clean-code), architecture and boundaries (Clean Architecture), professionalism and estimation (The Clean Coder), agile values and practices (Clean Agile), and design-pattern use vs misuse. Use it to evaluate structure, dependencies, SOLID in context, code smells, and professional practices. It provides craft and design criteria only—not syntax or style enforcement, which remain the responsibility of your linter and formatter.

When to Use This Skill

• 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.

Aggregators by Source

Source	Focus	Where to go
Clean Code	Names, functions, comments, formatting, tests, classes, smells	Use @clean-code for detail; this skill references it for review/production.
Clean Architecture	Dependency Rule, layers, boundaries, SOLID in architecture	See reference.md and references/clean-architecture.md.
The Clean Coder