Pattern Library
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`.
Specification
- Skill ID
- owl-listener/designer-skills/pattern-library
- Publisher
- owl-listener
- Repository
- designer-skills
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
How to use it
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
owl-listener/designer-skills/pattern-libraryInstalls these files- SKILL.md
What this skill tells the agent
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
More from owl-listener
Use this skill in a project
Open any RiverX project, search the Skills panel for owl-listener/designer-skills/pattern-library, and install it in one click.
