excellence-skill-creatorlisted

Design-excellence skills transform Claude from a generic pattern-matcher into an opinionated craftsperson. A skill without strong opinions is just documentation with delusions of grandeur. The user provides a domain (e.g., "API design", "error messages", "database schemas") and context about what makes generic output unacceptable. If they can't articulate why generic output fails, help them find that angle first—it's the foundation of everything that follows. <excellence_philosophy> ## Philosophy: What Makes a Design-Excellence Skill A design-excellence skill without these five traits is just documentation pretending to have opinions: 1. **Force intentional choices**: Make Claude commit to a direction before touching the keyboard. Intentional choices produce distinctive output; default choices produce forgettable output. 2. **Encode taste, not just rules**: Rules tell you what's legal. Taste tells you what's *good*. Your skill transmits the judgment of someone who has failed enough times to know what actually matters. 3. **Name the anti-patterns**: Claude knows thousands of patterns. Tell it which ones are tired, overused, or inappropriate for this context. The anti-patterns block is often the most valuable section—it's where your hard-won experience becomes actionable guidance. 4. **Define done**: Success criteria prevent the "good enough" trap. If you can't measure it, Claude will satisfice. Measurable outcomes distinguish excellent from adequate. 5. **Match complex