component-spec

Component specifications define structure, variants, and interaction states to align design teams and engineers. This Skill generates structured Markdown outlining anatomy, props, states, and accessibility rules to reduce ambiguity and rework.

Design system component documentation should include anatomy, variants, props, states, behavior, accessibility, and usage guidelines. This ensures teams have a clear, implementable plan that reduces ambiguity and rework during development handoff.

Accessibility guidelines for component variants require documenting ARIA roles, keyboard navigation, and focus management. This Skill generates these rules alongside usage guidelines to ensure robust and inclusive design system components.

Yes, you can generate a structured component API specification by defining required versus optional fields. This Skill outputs a structured Markdown body that explicitly outlines the Props/API surface for your design system components.

Yes, this approach works for documenting responsive behavior and component governance by applying the specification structure. It ensures consistent rules across anatomy, variants, states, and usage guidelines throughout the design system.

The best way to structure a component specification is using a Markdown body with frontmatter for name and description. The body should outline overview, anatomy, variants, props, states, behavior, and accessibility.