The Dependency Rule: source code dependencies point inward. Business logic owes nothing to frameworks.
About the book
Uncle Bob moves up the stack. SOLID principles, component cohesion and coupling, and above all the Dependency Rule — keeping business logic isolated from frameworks, databases, and UIs. Pairs beautifully with A Philosophy of Software Design. The book that explains why so many microservices architectures quietly fail.
Best used for
—Deciding where business rules belong in a layered system
—Structuring a new backend so frameworks stay as plugins
—Reviewing whether your Use Cases are truly independent of delivery mechanisms
“I spent three years thinking microservices were the answer. This book explained clearly why I kept failing.”
— dev.to
Install this skill
Run this command in your terminal. The skill will be available in all your Claude Code projects.