What problem does it solve? Code reviews often stall on vague feedback or rigid rule-checking against SOLID principles recited without understanding. This Skill gives you a shared, qualitative vocabulary — Composable, Unix philosophy, Predictable, Idiomatic, Domain-based — for judging whether code is ergonomic, trustworthy, and aligned with its problem domain. ## Core Features & Use Cases - Five-property evaluation lens: Assess any module, class, or function against Composability, Unix philosophy, Predictability, Idiomaticity, and Domain-fit, each with concrete smells and heuristics. - SOLID comparison and integration: Map CUPID properties to SOLID principles so both frameworks can be used as complementary lenses in design discussions. - Use Case: During a code review, instead of saying "this feels off," you can state precisely: "This service isn't composable because it imposes its framework on callers, and its behavior is unpredictable due to hidden side effects." ## Quick Start Ask Claude to review a class or module against the CUPID properties and identify which qualities are missing.