Skip to content
Back to skills

Component Spec

ASecurity

Write a detailed component specification including props, states, variants, accessibility requirements, and usage guidelines.

  • 158 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
designapi

Works with

  • api

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add NVlabs/Skill2Env --skill component-spec --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Component Spec?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Component Spec
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-component-spec/badge)](https://www.skillsdirectory.com/skills/nvlabs-component-spec)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: component-spec
description: Write a detailed component specification including props, states, variants, accessibility requirements, and usage guidelines.
---
# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…