Lean and assumption-respecting: no padding with concepts Claude already knows, each section (Ritual, Ideal Call Site, Mental Inlining, Go Up One Level, Asymmetric Check, Decision Rules, Output Shape) carries a distinct concrete template.

Provides concrete, copy-ready artifacts — the Ritual txt block, the ideal-call-site questions, the inlining keep/inline checklist, explicit take-vs-keep decision rules, and an Output Shape template — not vague direction.

"The Ritual" is a clearly sequenced pre-coding pass (Current path → Friction → Radical option → Deletion prize → User loss → Decision) and Decision Rules supply the checkpoint; this is a design skill so the destructive/batch validation cap does not apply.

Well-organized single file with one-level cross-skill links, but there are no bundle files and at ~165 lines (above the 50-line simple-skill threshold) all content is inline with no material split out into references.

Lists multiple concrete actions — "state the current path, invent the cleanest from-scratch option, inline suspicious layers, find asymmetric deletions, and choose the option that makes the system easiest to explain" — matching the multi-action anchor.

Explicitly answers both: the "Use when..." trigger clause covers when, and "Forces a higher-level pass before coding: state the current path..." covers what.

Covers natural phrases a user would actually say ("think bigger", "redesign from scratch", "go up a level", "consider radical options", "a fix keeps spreading across layers"), with only minor jargon ("mentally inline", "asymmetric deletions").

Occupies a clear niche (escaping a bad abstraction via radical redesign) and explicitly delegates overlapping cases to sibling skills, keeping triggers distinct.