clean-code

Start with the 10-question diagnostic checklist covering naming, function length, error handling, and test coverage. Then score the code on the 0-10 scale and apply targeted fixes like guard clauses for nested conditionals or the Rule of Three for duplication.

The Rule of Three says to tolerate duplication once and only abstract when the same logic appears a third time. Abstracting on the second occurrence risks creating a wrong abstraction that must be unwound later.

Yes, the Skill includes language-specific examples for Python and TypeScript covering type annotations, guard clauses, null handling with Optional types, and test naming conventions. It also notes adaptations for Go, Rust, and functional languages.

Performance-critical code like game engines or embedded systems may accept longer functions when abstraction costs are prohibitive. Framework conventions also take priority, and any divergence from a principle should be documented explicitly.

Push null checks to the boundary by validating once at the entry point, then pass valid objects downstream. Use Optional types where available, or apply the Null Object Pattern to provide a safe no-op substitute for absent values.