component-spec

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): <!-- shared:mandatory-context-bootstrap --> - 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 toke...