pattern-library — Claude Code skill: what it does, how to install
This skill turns recurring UX solutions into pattern entries with problem context, behavior, examples, accessibility notes, and related patterns.
npx skills add Owl-Listener/designer-skills --skill pattern-library -a claude-codeWhat pattern-library does
pattern-library structures documentation for recurring UX problems. Each pattern entry can capture the problem statement, solution, anatomy, required and optional elements, context-specific variants, and responsive adaptations.
It also covers user flow, state changes, error handling, good implementations, anti-patterns, accessibility, assistive technology support, and related patterns. Entries can be organized under navigation, input, display, feedback, and onboarding. The format is meant to preserve design knowledge for reuse.
This skill is for patterns rather than a single component API. That distinction matters: the source assigns component-level API documentation to component-spec.
What it helps with
- document a recurring UX problem
- structure a reusable pattern entry
- describe variants and interface behavior
- record good implementations and anti-patterns
- connect a pattern with related solutions
Example prompts for the agent
- Create a pattern entry for an empty state with the problem, solution, variants, behavior, and accessibility sections.
- Document a navigation pattern with good implementation examples, anti-patterns, and related patterns.
- Review this pattern entry and add error handling, responsive adaptations, and assistive technology support.
How to install pattern-library
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill pattern-library -a claude-code2Manually: put the files in place
~/.claude/skills/pattern-library/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pattern-library/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill pattern-library -a codex2Manually: put the files in place
.agents/skills/pattern-library/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill pattern-library -a cursor2Manually: put the files in place
.cursor/skills/pattern-library/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills pattern-library2Manually: put the files in place
.github/skills/pattern-library/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill pattern-library -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path design-systems/skills/pattern-libraryManually: put the files in place
.devin/skills/pattern-library/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill pattern-library -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pattern-library
How do I install pattern-library in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill pattern-library -a claude-code, then run npx skills add Owl-Listener/designer-skills --skill pattern-library -a claude-code again. The skill file is at ~/.claude/skills/pattern-library/SKILL.md.
What does pattern-library do?
It creates structured entries for recurring UX solutions. The entry can cover the problem, solution, anatomy, variants, behavior, examples, accessibility, and related patterns.
How is pattern-library different from component-spec?
pattern-library documents recurring solutions and their context. component-spec is used for the API of a single component.
Source text
SKILL.md · MIT
--- name: pattern-library description: Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use `component-spec`. --- # Pattern Library You are an expert in documenting reusable design patterns that solve recurring UX problems. ## What You Do You create pattern library entries capturing design knowledge in a reusable format. ## Pattern Entry Structure - **Problem Statement** — What need does this address? What contexts? - **Solution** — The pattern, key principles, visual/interaction description - **Anatomy** — Components, layout, required vs optional elements - **Variants** — Context-specific implementations, responsive adaptations - **Behavior** — User flow, state changes, error handling - **Examples** — Good implementations and anti-patterns with explanations - **Accessibility** — Inclusive design considerations, assistive tech support - **Related Patterns** — Similar patterns, commonly combined, builds upon ## Categories Navigation, input, display, feedback, onboarding ## Best Practices - Focus on problem first, solution second - Include real examples and anti-patterns - Connect patterns into a knowledge graph - Update as research reveals new insights
© Owl-Listener · MIT · Owl-Listener/designer-skills