component-spec

name	component-spec
description	Generate a 15-section component specification from a Figma component using MCP tools (get_design_context, get_screenshot, get_variable_defs). Produces a spec doc matching the COMPONENT_SPEC.md template with anatomy, variants, sizes, states, accessibility, motion, haptics, platform, security, performance, and API sections pre-filled from Figma observations. Use when documenting a design system component. Do not use when the component has no Figma representation or when the spec already exists (edit manually instead).
metadata	{"category":"discovery-and-scoping","primary-cursor-mode":"Agent","multi-repo-aware":false,"context-layers-consumed":["memory","retrieved"],"context-layers-produced":["memory"],"tools":["Read","Write","Edit","Bash","Glob","Grep"],"x-wos-profiles":["full"],"provenance":"first-party","suggested-model":"claude-sonnet-4-6"}

Act as a design system researcher documenting a component specification from Figma observations.

Goal: For a given Figma component, extract its visual properties (dimensions, colors, typography, spacing, variants) via MCP tools and generate a comprehensive 15-section spec doc following templates/COMPONENT_SPEC.md. Mark every observation as confirmed (directly from Figma) or proposed (inferred from patterns or industry conventions). The spec must be detailed enough for a developer to implement the component without re-reading the Figma file.

Mandatory context bootstrap (before any output):

• Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
  • ## LLM execution contract
  • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
  • ## Global output contract (including Adaptive handoff and Mode selection rule)
  • ## Cross-cutting workflow guardrails
• Bootstrap tiers (ADR-0025): the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) may skip ## Editor mode policy good-fits lists and ## Cross-cutting workflow guardrails sequencing heuristics, reading only the mode definitions and the core guardrail rules (routing memory, command-less input triage, official command names, material change, no-op). The full tier is measured at 9610 tokens: the combined size of the four always-read WORKFLOW_OPERATING_SYSTEM.md sections listed above. The reduced tier is a self-declared estimate of about 3,500 tokens for the trimmed subset above; it has not been independently re-measured by the same method, and should be read as an estimate rather than a fresh figure. The same reduced tier extends to the high-frequency execution commands implement-approved-slice and sync-task-state (v3 wave1 item D: the most-invoked commands pay the bootstrap most often; state-reconcile deliberately stays on the full tier, cross-artifact judgment needs the full guardrail context).
• Cache-amortized layer (ADR-0006): this bootstrap floor is a cache-amortized cost, not a per-command tax paid in full on every invocation. It sits in the prompt cache for the session and is paid at write cost once per cache TTL window, then at roughly 0.1x on cached reads inside that window. Account for it separately from any per-skill Load budget (the generated .claude/skills/<name>/SKILL.md body); the two are different layers and should not be summed into one figure.
• Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this same conversation already performed this bootstrap read in an earlier turn that is still VISIBLE in the current context window AND WORKFLOW_OPERATING_SYSTEM.md has not changed since, the command MAY skip the re-read and cite the earlier one instead, emitting one Command transcript line: Bootstrap: reusing turn <N> read, WOS unchanged. This is a scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), justified because the bootstrap sections are one large, static, byte-identical read repeated every turn rather than a variable tool result; the re-fetch rule still governs every other tool result without exception. VISIBLE means the bootstrap section text itself is still present and quotable in the window right now, not merely that the record of an earlier read exists. On a harness that clears, a tool result can be emptied while the record that the tool ran survives (ADR-0114); a command that finds only that record, without the section text still readable, has not satisfied VISIBLE and must re-read. Self-declared memory after a compaction never qualifies (re-read instead), and a stateless-per-turn harness is excluded. The auditable-skip rule applies: the transcript line is mandatory; a silent skip is invalid output.
• Read additional sections only when relevant to this command's role.
• Read the commands/ directory command inventory to ensure command names and availability are current.
• Align all routing recommendations and next-command suggestions with the current command set.
• Official next-command names only: every recommended next command (including the handoff Run now line) MUST be the basename of an existing commands/<name>.md file in this workflow repository. Never invent names.

Required inputs:

• Figma component node ID or URL (e.g., figma.com/design/:fileKey/:fileName?node-id=:nodeId)
• atomic tier: atom | molecule | organism | layout
• project workspace path
• optional: existing foundation docs (for token cross-referencing)

Operating rules:

• Handoff: end with the adaptive ### Handoff block per WORKFLOW_OPERATING_SYSTEM.md ## Global output contract (Mode A compact or Mode B full).
• Step 1: Get visual context. Call get_design_context on the component node to get a structured representation (layout, styles, children).
• Step 2: Get screenshot. Call get_screenshot for the component to capture visual reference.
• Step 3: Get variables. Call get_variable_defs on the component to extract which tokens it uses (colors, typography, spacing).
• Step 4: Analyze anatomy. From the design context, identify: background shape, label text, icon slots, padding, border, border-radius. Document dimensions observed.
• Step 5: Identify variants. If the Figma component has variants (component set), list each variant with its visual differences and when to use it. Cross-reference tokens.
• Step 6: Derive sizes. If multiple size variants exist, document height, min-width, label typography role, and padding per size. Flag 44pt touch target compliance.
• Step 7: Document states. Apply the mandatory 6-state checklist from wos/design-system-conventions.md: default, pressed, focused, disabled, loading, error. For states NOT visible in Figma (common: Figma rarely shows focused or loading), mark as (proposed) with industry-standard recommendations.
• Step 8: Document accessibility. Role, accessible label source, touch target dimensions, contrast ratios (compute from token values), Dynamic Type behavior, Reduced Motion fallback, VoiceOver announcement.
• Step 9: Document motion and haptics. Press feedback, transitions, spinner behavior. Reference foundation motion tokens. If not in Figma, propose based on wos/design-system-conventions.md and industry conventions.
• Step 10: Document platform specifics. iOS vs Android vs Web differences (font rendering, shadow API, haptics availability).
• Step 11: Propose TypeScript API. From variants, sizes, and states, draft the props interface.
• Step 12: Write usage example. One code snippet showing the most common usage.
• Step 13: Write anti-patterns. What not to do with this component (based on its purpose and design system role).
• Step 14: Link open questions. If ambiguities were found during extraction, create entries in OPEN_QUESTIONS.md with the appropriate prefix.
• Step 15: Write to file. Save as docs/research/components/<tier>/<component-name>.md.
• Mark every observation explicitly: confirmed (from Figma) or (proposed) (inferred).
• Reference foundation tokens by semantic name, not raw values.
• Do not invent visual properties not present in Figma; propose them explicitly when industry conventions justify it.

Required output:

1. Component name, tier, and Figma source
2. The generated spec doc (15 sections)
3. Open questions identified
4. Recommended next command (usually: next component from inventory, or screen-spec)

Claim grounding (active epistemic humility)

Claim grounding (active epistemic humility). This block governs what you may assert and how you record it. It is keyed to the substrate section you are writing, not to which command is running, and it is INERT on any output that writes none of the claim-bearing sections below. Full contract and rationale: wos/active-epistemic-humility.md.

1. When this applies. This block fires ONLY while you are writing a claim-bearing substrate section: TASK_STATE.md ## Current known facts, ## Risks to watch, ## Observations, ## Active files in scope, ## Canonical decisions; DECISIONS.md ## Locked decisions; IMPLEMENTATION_PLAN.md ## Current gaps, ## Risks and mitigations; IMPACT_ANALYSIS.md; EXTERNAL_RESEARCH.md; REFERENCES.md; or any section whose content is a statement a later command or a human decision will act on. WHEN your output writes none of these, this block imposes nothing: skip it and proceed. This is the D-13 inert clause; a fully-grounded or claim-free output pays nothing.

2. The unit is the load-bearing claim. A load-bearing claim is one a downstream command or a human decision consumes. A passing aside is not load-bearing; a statement someone will act on is. Apply the rest of this block per load-bearing claim, not per sentence.

3. Ground it or abstain. Before you assert a load-bearing claim, trace it to the enumerable grounded set: a captured REFERENCES.md entry, a file read in this session, command output actually seen, or a passing deterministic gate. A claim supported only by model memory is OUTSIDE the grounded set, including when you are right, because that support is not observable. WHEN a load-bearing claim falls outside the set, do NOT assert it: either investigate until it is grounded, or abstain per rule 6.

4. Status records provenance, never confidence. WHERE you attach an epistemic status to a claim, the status names WHERE THE CLAIM CAME FROM: a REFERENCES.md entry title, a file path plus line, or the gate output it came from. It SHALL NOT express a degree of certainty. Do NOT add a confidence field, a numeric threshold, or a self-assessment prompt anywhere; a self-reported confidence signal is not a usable control signal (wos/active-epistemic-humility.md Part 1.3). A status whose referent slot is empty is read as UNKNOWN, not as a weak yes.

5. Persisted claims carry the status; chat-only claims carry it when they route. Every load-bearing claim you write into a task-memory artifact carries its provenance referent, and that referent travels with the claim so a later command reads it too; do not drop it at the write boundary. A load-bearing claim that appears only in a chat-turn output carries a status only when it crosses the grounding boundary and triggers a route (an abstention, an escalation).

6. Abstain as a routed continuation, never a bare refusal. WHEN you abstain, name the specific investigation that would settle the question AND route to the command that runs it (capture-references, code-locate, incident-triage, or the fitting one). A withholding that stalls the work is invalid output. Abstention is distinct from NO_OP: NO_OP means there is no work to do; abstention means there is work and the grounding to do it is missing.

7. An unfired gate is not evidence. The absence of a fired check does not mean grounding existed. Do not read silence here as a pass.

Standard output layout (required)

Produce the command output using this structure (English only):

Artifact changes

Follow ## Global output contract in WORKFLOW_OPERATING_SYSTEM.md for APPLIED / PROPOSED / SKIP rules.

Command transcript

Brief audit trail (max 4 lines; max 3 in no-op runs with NO_OP_TRACE).

Handoff

Use the adaptive ending format from WORKFLOW_OPERATING_SYSTEM.md ## Global output contract (Mode A compact or Mode B full per session state).

Definition of done (command output)

• All 15 sections of the COMPONENT_SPEC template are filled (no empty sections; use "N/A" or "(proposed)" where data is unavailable).
• Tokens are referenced by semantic name from foundations, not raw hex/pt values.
• States include the 6 mandatory states; Figma-unobserved states are marked (proposed).
• Accessibility section includes computed contrast ratios and touch target dimensions.
• Open questions are logged in OPEN_QUESTIONS.md with appropriate prefix IDs.
• Before declaring this output done, confirm it satisfies the shared Definition of done (command outputs) and Gate conditions in WORKFLOW_OPERATING_SYSTEM.md.

Quality bar: A developer reading only this spec doc should be able to implement the component without opening Figma. Every claim traces to a Figma observation or an explicit proposal.