Agent skill

Pattern Library Skill: Document Reusable UI Patterns

The pattern library skill helps an AI agent write pattern entries with a problem statement, solution, anatomy, variants, behaviour, examples, accessibility notes and related patterns.

Install
/plugin marketplace add Owl-Listener/designer-skills
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the pattern library skill?

Pattern library is a skill in the Owl-Listener designer-skills repository. It helps an AI agent document a recurring design solution as a structured entry: problem statement, solution, anatomy, variants, behaviour, examples, accessibility and related patterns. For one component's API, the repo points to component-spec.

It is a short, focused skill in the design-systems plugin of the Designer Skills Pack. Its job is to turn a recurring UX problem into a reusable pattern entry, so design knowledge is written down in one consistent format.

The skill description separates it from a component: use it when documenting a recurring solution, and use the component-spec skill when you need a single component's API. The skill file is brief, so expect structure rather than depth.

The structure of an entry

  • Problem statement: the need and the contexts it appears in.
  • Solution: the pattern, its key principles and a visual or interaction description.
  • Anatomy: components, layout, and which elements are required or optional.
  • Variants: context-specific versions and responsive adaptations.
  • Behavior: user flow, state changes and error handling.
  • Examples: good implementations and anti-patterns, with reasons.
  • Accessibility and related patterns.

Who the pattern library skill is for

Best for

  • Design system teams recording patterns such as navigation, input, display, feedback and onboarding.
  • Designers who want an agent to draft entries in a fixed template.
  • Teams building a knowledge graph of patterns that link to each other.

Not for

  • Documenting one component's props and states.
  • Generating code. It writes documentation, not implementation.
  • Finding patterns for you. You supply the problem and examples.

Use it with UiChemy

A pattern entry describes a solution; building it on WordPress is a separate step. UiChemy Figma to WordPress converts designs into editable pages. Click Get Started on uichemy.com.