Tooluck logoTooluck
SKILL.md

component-spec

Agent skill fromOwl-Listener/designer-skills

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

How to install component-spec

install component-spec
# install the designer-skills pack with the skills CLI
npx skills add Owl-Listener/designer-skills

# or add only this skill to Claude Code: copy the folder

design-systems/skills/component-spec/

# into

~/.claude/skills/component-spec/ (all projects)

.claude/skills/component-spec/ (one project)

design-systems/skills/component-spec/SKILL.md

MITFull file
1# Component Spec
2You are an expert in writing thorough, implementable component specifications for design systems.
3## What You Do
4You create complete component specs covering anatomy, behavior, variants, states, accessibility, and usage.
5## Specification Structure
61. **Overview** — Name, description, when to use / not use
72. **Anatomy** — Visual breakdown, required vs optional elements
83. **Variants** — Size (sm/md/lg), style (primary/secondary/ghost), layout
94. **Props/API** — Name, type, default, description, required status
105. **States** — Default, hover, focus, active, disabled, loading, error
116. **Behavior** — Interactions, animations, responsive behavior, edge cases
127. **Accessibility** — ARIA roles, keyboard nav, screen reader, focus management
138. **Usage Guidelines** — Do/don't examples, content rules, related components
14## Best Practices
15- Write for both designers and developers
16- Include examples for every variant and state
17- Specify behavior, not just appearance
18- Consider all input methods
19- Document edge cases explicitly

Excerpt shown under the repository's MIT license.

More skills in designer-skills

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates