Clean Code

Systematically audit code for naming honesty, function clarity, class cohesion, SOLID violations, and comment necessity. Code is read far more than it is written — clean code respects the reader.

Skill workflow — clean code and tests reinforce each other: clean-code (make it readable) → tdd (make it testable — same virtue) → techdebt (remove accumulated mess)

Philosophy

"Clean code reads like well-written prose." — Robert C. Martin

Clean code is not about aesthetics. It's about reducing the cognitive load required to understand, change, and extend the code. Every act of obfuscation — a vague name, an oversized function, a class with mixed concerns — is a tax on every future reader.

The fundamental question for every code element: does this tell the truth?

• Does the function name tell you what it does — fully, honestly, without reading the body?
• Does the class name tell you its single responsibility?