agentsclimarketplace

Component spec

Skill Dragoon0x/studio/skills/component-spec

Write a complete component specification including api, states, variants, accessibility, and usage. Use whenever the user needs a component spec, component documentation, component api design, or is designing a new component for a design system.From its SKILL.md

Install
npx -y skills add Dragoon0x/studio --skill component-spec

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, as published. Nobody here has run it

component-spec

a complete spec for one component. covers what it is, how to use it, what props it takes, every state it can be in, and how it behaves.

structure

# [ComponentName]

## purpose
one sentence: what this component is for.

## when to use
specific scenarios where this is the right component.

## when not to use
common misuses, with alternatives.

## anatomy
labeled diagram (described in markdown) of the visible parts.

## props / api
| prop | type | default | required | description |

## variants
- size: [list]
- style: [list]
- state: [list]

## states
- default
- hover
- focus
- active
- disabled
- loading
- error
- empty
each with a one-line description of the visual and behavior.

## accessibility
- role
- keyboard interactions (key + behavior)
- aria attributes used and why
- focus management
- screen reader behavior

## composition
- what this component is made of (other components, primitives)
- what this component can contain (slots, children)

## examples
3-5 usage examples covering common cases.

## related components
- when to use [X] instead
- often paired with [Y]

what to avoid

  • describing visual style in prose. show tokens.
  • inventing props you don't need yet.
  • copying from other libraries without considering your own conventions.
  • listing every possible variant when only three are commonly needed.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.