clean-code

Clean Code

Author: Robert C. Martin (Uncle Bob) | Pages: ~462 | Chapters: 17 | Generated: 2026-08-24

How to Use This Skill

• No arguments — load core frameworks for reference (this file's Core Frameworks section).
• With a topic — ask about naming, functions, comments, TDD, error handling, code smells, etc.; I find and read the relevant chapter.
• With a chapter — ask for ch03 (functions) or ch17 (smells); I load that specific chapter file.
• Browse — ask "what chapters do you have?" to see the full index.

When you ask about a topic not covered in the Core Frameworks below, I will read the relevant chapter file before answering, grounded in the book's actual content.

Language-agnostic: The principles in this skill are universal software-engineering truths, not Java rules. The book happens to use Java for its code examples, but naming, functions, comments, SRP, TDD, error handling, concurrency, and code smells apply to every language. When you name a language (e.g. "in Rust", "in Go"), I will translate the advice to that language using appendix-lang-map.md instead of quoting Java syntax.

---

Core Frameworks & Mental Models

Clean Code is a discipline of care: code is read far more than it is written (reading:writing ≈ 10:1), so optimize for the reader. Below are the author's named, reusable frameworks — apply them, don't just recall them.

Professionalism & attitude

• The Boy Scout Rule — Leave the campground cleaner than you found it. Every check-in makes one small, safe improvement (rename, extract, de-dupe). Cumulatively this prevents rot; you never need a "Grand Redesign in the Sky".
• LeBlanc's law — "Later equals never." Refactoring deferred to "later" is refactoring never done. Fix it where you stand.
• The Primal Conundrum — Making a mess to hit a deadline guarantees you miss it; the only way to go fast is to keep the code clean. Refuse requirements that force chaos (Semmelweis hand-washing analogy).