Turns out documenting design patterns properly is harder than most teams think, and this skill gives you a structured way to do it right. It walks you through creating pattern library entries that start with the problem context, then cover the solution anatomy, variants, behavior states, accessibility considerations, and connections to related patterns. The format pushes you to include both good examples and anti-patterns with explanations, which is honestly the most useful part since that's what people actually need to see. If you're building or maintaining a design system and tired of patterns being documented inconsistently or missing critical details, this gives you a repeatable template that captures the knowledge properly.
npx skills add https://github.com/owl-listener/designer-skills --skill pattern-library