CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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`.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-systems/skills/pattern-library/SKILL.md
SKILL.md
Quality
Evals
Security

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
Repository

Owl-Listener/designer-skills

Path

design-systems/skills/pattern-library/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.