Clean Code, Clean Architecture & Clean Craftsmanship

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY in this skill are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in all capitals.

A working guide to Robert C. Martin's principles. The aim is not to recite rules — it's to make code that the next person (often you, in six months) can read, change, and trust without fear. Messy code always slows you down; the only question is when. The fastest way to ship is to keep the code clean.

But clean means as simple as the problem allows, never as elaborate as possible. The single most common way to misapply these principles is to over-build — wrapping a 20-line script in layers it doesn't need. Read Right-size the solution below before you reach for any pattern.

This file (L1) holds the everyday rules for code you write or review; apply them in proportion to the change in front of you. The deeper material lives in references/ — pull a file in only when the task calls for it (see Going deeper at the bottom).