SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Document recurring design solutions with context, usage examples, and related patterns.
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`.
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
Original instructions from the publisher’s SKILL.md
# 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