Clean Code

This is Robert C. Martin's Clean Code handbook distilled into 48 rules across naming, functions, comments, formatting, and error handling. It triggers during code reviews, refactoring, and when you're debating what to call something. The rules are prioritized by impact, so you know meaningful names and small functions matter more than test patterns. Examples are Java-heavy but the principles translate. The skill includes modern corrections where Uncle Bob's 2008 advice has aged poorly. Honestly most useful as a shared vocabulary for code review discussions rather than gospel, since some rules like "one assert per test" remain contentious fifteen years later.