Skill Store 33

Component Spec

Specify one component — props, states, variants, accessibility, and usage rules.

by owl-listener · MIT

The skill

Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use `pattern-library`.

Component Spec

You are an expert in writing thorough, implementable component specifications for design systems.

What You Do

You create complete component specs covering anatomy, behavior, variants, states, accessibility, and usage.

Specification Structure

  1. Overview — Name, description, when to use / not use
  2. Anatomy — Visual breakdown, required vs optional elements
  3. Variants — Size (sm/md/lg), style (primary/secondary/ghost), layout
  4. Props/API — Name, type, default, description, required status
  5. States — Default, hover, focus, active, disabled, loading, error
  6. Behavior — Interactions, animations, responsive behavior, edge cases
  7. Accessibility — ARIA roles, keyboard nav, screen reader, focus management
  8. Usage Guidelines — Do/don't examples, content rules, related components

Best Practices

  • Write for both designers and developers
  • Include examples for every variant and state
  • Specify behavior, not just appearance
  • Consider all input methods
  • Document edge cases explicitly

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: owl-listener/component-spec-94573600847.

Download SKILL.md · Markdown version

Details

Publisher
owl-listener
Category
Software Development › Frontend & UI
License
MIT
Updated
2026-09-05

References

More from owl-listener

  • Design Critique Facilitate a structured team critique — framing, feedback rules, and actionable outcomes.
  • Design Debt Audit Inventory and prioritise accumulated design inconsistencies across a product.
  • Design Impact Reporting Communicate design's contribution to business and user outcomes in stakeholder language.
  • Design Qa Checklist Build a QA checklist for verifying that a build matches the design.

Related skills

  • Documentation Template Generate a reusable documentation scaffold for components, patterns, or guidelines.
  • Pattern Library Structure a pattern entry — problem context, solution, usage examples, and related patterns.
  • Component Library Guides React/Next.js component architecture for monorepos: naming, reuse, shared patterns.
  • Design Component Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, tok…
  • Core Components Core component library and design system patterns.