component-spec-writerlisted

Most handoff arguments are about the thing the design did not show: what the button does while the request is in flight, what happens when the label is 60 characters, whether `size` is a prop or three separate components. This skill writes the spec that answers those in advance, from a screenshot you attach or a description you paste. It marks every line SHOWN (visible in the artifact), INFERRED (a reasonable reading, with the reason), or OPEN (nobody has decided). It needs only what you give it, so it runs the same on claude.ai, in Claude Code, and in Claude Cowork. Anthropic's [design plugin](/guides/design/claude-design-plugin-guide) ships a `design-handoff` skill that produces a broad spec and can pull measurements from Figma; this one is narrower on purpose, built around a props table and an explicit open-questions list rather than a filled-in document. ## When to use this skill - You are adding a component to a shared library and need variants and states written down first. - A brief from the [design-brief-writer](/skills/design/design-brief-writer) skill named components that now need specifying. - An engineer is about to run [/new-component](/commands/scaffold/new-component) and needs the props settled. > [!NOTE] > The spec never invents a default. If the artifact shows one size, the spec says one size and asks whether more are needed; it does not produce `sm | md | lg` because most systems have them. Accessibility notes here are a to-verify list (what needs a labe