Design System Extractor

Design System Extractor

Act as a Design System Architect. Extract a reusable design-system package from visual and code references. Do not implement product screens during this skill unless the user explicitly chooses that after the checkpoint.

Supported Inputs

• Images / screenshots: use all provided screenshots as source of truth. Prefer concrete observed regions over general style impressions.
• Graphic design references: when inputs are flat visual references such as posters, banners, editorial layouts, ads, brand graphics, or social cards, extract reusable text compositions as typography evidence and as typographic component candidates when their structure can repeat in product UI.
• Figma URL / Figma exports: use available Figma tools or exported screenshots/metadata. When Figma MCP is available, use it to inspect referenced files/nodes and preserve MCP-ready source targets. Treat selected nodes, variables, and component names as evidence, but still record where each decision came from.
• Project / prototype folder: inspect rendered UI, screenshots, tokens, CSS, Storybook, and components. Treat prototype code as reference-only unless the user asks to migrate code.
• Mixed input: rank evidence in this order unless user says otherwise: production Figma/component library, production screenshots, rendered project UI, prototype code, descriptive prompt.

First Actions

1. Locate or create a design-system package root.
2. Resolve this skill's folder as <skill-root>. Use <skill-root>/assets/... and <skill-root>/scripts/... when copying templates or running bundled scripts.
3. If the package has no structure yet, copy <skill-root>/assets/design-system-template/ into the target root.
4. Read existing AGENTS.md, CLAUDE.md, .cursorrules, .cursor/rules/*, and prior design-system/SESSION_STATE.md when present.
5. Inspect references before writing tokens. If a source project has screenshots and code, inspect both.

Workflow

1. Input Discovery

Record source types, paths/URLs, confidence, and known gaps in design-system/SESSION_STATE.md.

For screenshots, list every image. For Figma, list node/page names, component set names, variable collections, and MCP-ready identifiers when available. For project folders, list token files, component directories, Storybook entries, and screenshot/render routes if available.

Before using sources as evidence, run a source duplicate review:

1. Create a source fingerprint for every input and record it in design-system/DESIGN_EVIDENCE_MAP.md.
2. For local screenshots or exports, prefer sha256:<hash> for exact matches and add phash:<hash> or a screenshot crop note when perceptual comparison is available.
3. For Figma inputs, keep the original Figma URL, record the canonical node/design URL when known, and normalize the fingerprint to figma:<file-key>#<node-id> when a node is known, or figma:<file-key>#page:<page-name> when only a page is known. Use MCP node-id form with : in fingerprints and retain URL node-id form with - in the URL.
4. For rendered routes or project screenshots, include the route, viewport, state, and source file or command in the fingerprint.
5. If two sources are exact duplicates or likely duplicates, stop and ask the developer whether to reuse existing source, ignore duplicate, or keep distinct.
6. Record every decision in design-system/DESIGN_EVIDENCE_MAP.md under Source Duplicate Review before using duplicate inputs to support separate design decisions.

2. Evidence Map

Fill design-system/DESIGN_EVIDENCE_MAP.md before writing final design decisions.

Each important decision needs an evidence row with:

• source file, URL, node, or route
• MCP-ready Figma target when the source is Figma
• observed region
• observed pattern
• resulting design decision
• affected tokens or components
• confidence: High, Medium, or Low

Use references/visual-analysis-rubric.md when evaluating screenshots or rendered UI.

For Figma sources, DESIGN_EVIDENCE_MAP.md must preserve enough information for a downstream agent to call Figma MCP without re-discovering the source:

• original file/design URL
• canonical node URL with node-id when available
• file key
• node id in MCP form, such as 12:34
• page, frame, selected node, and component set names when known
• suggested MCP read path, usually get_design_context and get_screenshot for component nodes, get_metadata for page-level sources, and get_variable_defs for variable collections

If Figma MCP is unavailable during extraction, still record the URL, page/frame/node names visible from the prompt or export metadata, and mark the MCP target as unresolved - MCP unavailable instead of dropping the trace.

3. Design Foundations

Fill design-system/DESIGN_PRINCIPLES.md and design-system/DESIGN_ELEMENTS.md.

Cover color proportions, typography, text composition, spacing, density, shape, elevation/depth, iconography, imagery, data display, and state language. Every principle must include evidence and an implementation rule.

For graphic design references, inspect typography as composed structures, not only individual type tokens. Capture repeated or reusable combinations such as headline + kicker, headline + deck, eyebrow + title + body, price + qualifier, metric + label, caption overlays, editorial pull quotes, CTA text clusters, and stacked brand statements. Record hierarchy, line breaks, alignment, rhythm, optical spacing, case, tracking, max line length, emphasis, and relationship to nearby imagery or containers.

4. Token Architecture

Fill design-system/TOKEN_ARCHITECTURE.md and token files under tokens/.

Default to strict ref -> sys -> comp inheritance when the project has no stronger convention:

• reference tokens store raw values only
• system tokens store shared semantic roles only
• component tokens store component slots only
• component tokens reference system tokens only

Use references/token-architecture.md before creating or changing token layers.

Before finalizing token files, run a token candidate review:

1. Collect raw color, spacing, radius, typography, opacity, shadow, and motion values from evidence.
2. Normalize reference colors into palette families with numeric steps where 100 is lightest and 0 is darkest.
3. Check each palette family so higher numbers are visually lighter than lower numbers.
4. Cluster very close reference colors and very close reference numbers in the same value family.
5. Check exact system-token aliases in the same semantic dimension and exact component-token aliases in the same component/dimension. Treat them as review candidates unless a documented semantic reason exists.
6. Build a token inheritance graph for ref -> sys -> comp, resolve each system/component token to its raw reference value, and compare purpose fingerprints before deduping. Purpose fingerprints include layer, semantic role, component name/category, slot/anatomy, state, resolved raw value, and inheritance chain.
7. For system tokens, review pairs only when the semantic role/category and resolved value are close enough. For component tokens, review pairs only when component category, slot/category, state, and resolved value are close enough.
8. If close or duplicate candidates appear, stop and ask the developer whether to merge or keep distinct.
9. Record every decision in design-system/TOKEN_ARCHITECTURE.md under Near Token Decisions, or add an adjacent token-review: CSS comment when the decision must stay next to the token.
10. Only then write final ref, sys, and comp tokens.

5. Component Inventory

Fill design-system/COMPONENT_INVENTORY.md.

Inventory repeated patterns from the references. Mark each component as extracted, planned, blocked, or out-of-scope. Include priority, observed sources, required token groups, missing states, and implementation notes.

Treat reusable text compositions as component candidates even when they come from flat graphic references rather than app UI. Name them with typographic- or a clear product role, such as typographic-hero-lockup, typographic-section-heading, typographic-metric-pair, typographic-price-stack, typographic-caption-overlay, or typographic-pull-quote. Mark them extracted when the component spec and component tokens exist, planned when the visual structure is observed but implementation details need another pass, and out-of-scope only when the text treatment is clearly one-off artwork.

Before finalizing inventory or adding a new component spec, run a component similarity review:

1. Read existing COMPONENT_INVENTORY.md, design-system/components/*.md, and relevant component tokens.
2. Create a component fingerprint for each new candidate: purpose, anatomy, variants/states, token contract, layout/density, behavior, source evidence, and visual reference.
3. Compare the candidate with existing extracted or planned components. Weight purpose and behavior first, then anatomy, states, token usage, and layout.
4. Run node <skill-root>/scripts/audit_components.mjs <target-root> during extraction to surface automatically detected fingerprint similarities before strict checkpoint.
5. If a candidate is similar to an existing component, stop and ask the developer whether to merge, make variant, keep distinct, or block pending more evidence.
6. Record the decision in COMPONENT_INVENTORY.md under Component Similarity Review before creating or updating component specs.
7. Use source-based visual references: for Figma, capture the actual node preview/screenshot or a crop of the design frame; for screenshot inputs, crop the relevant component region. Store review images under design-system/assets/component-review/ and link them from the similarity table.
8. Do not use an AI-drawn schematic as the review image when a Figma preview or screenshot crop is available. A schematic SVG is allowed only as a last-resort fallback when source previews cannot be captured, and it must be labeled schematic fallback - source preview unavailable; it is not design evidence.

6. Component Token Specs

Extract at least one high-value component when the user did not specify one, usually the primary action component for product UI or the most reusable typographic composition for graphic design references. Extract additional repeated shell/navigation components when they are central to the reference.

For each extracted component, create design-system/components/<component-name>.md from design-system/COMPONENT_SPEC_TEMPLATE.md and update tokens/tokens-comp.css. Use lowercase hyphen-case filenames, such as primary-button.md or bottom-navigation.md.

For each component spec, fill Source Trace whenever source material exists. Include the exact Figma node or design URL, Figma MCP target (fileKey, nodeId, page/frame/node names, suggested MCP calls), screenshot crop/export path, rendered route with viewport/state, prototype/source files, and existing product component candidates. If a trace type is unavailable, mark it not available with a short reason instead of leaving it ambiguous.

When a component comes from Figma, do not treat a screenshot crop as a replacement for the Figma source trace. The crop is a visual reference; the Figma URL and MCP target are the handoff path for downstream implementation.

Use references/component-spec-rules.md for anatomy, variants, state coverage, accessibility, and token naming.

For typographic components, the spec must define text slots, hierarchy, responsive wrapping, line-count limits, alignment, spacing between text lines/groups, allowable emphasis, truncation rules, and content semantics. Component tokens should cover the composition slots, such as title, kicker, body, metadata, value, qualifier, divider, and caption, while mapping each slot back to system typography, color, spacing, and alignment tokens.

7. Composition, Interaction, And Anti-AI Rules

Fill or update:

• design-system/PAGE_COMPOSITION_RULES.md
• design-system/INTERACTION_STATES.md
• design-system/ANTI_AI_STYLE_RULES.md

Use references/page-composition-rules.md and references/anti-ai-style-rules.md.

The output must protect the observed product character. Do not add generic SaaS hero layouts, decorative gradients, glassmorphism, outline-card overuse, inflated whitespace, or unsupported illustration styles unless the references prove those patterns exist.

8. HTML Documentation

Generate developer-facing static HTML docs after design-system Markdown and token files are updated:

node <skill-root>/scripts/generate_docs_html.mjs <target-root>
node <skill-root>/scripts/generate_review_html.mjs <target-root>

Default outputs:

docs/design-system/index.html
docs/design-system/review.html

The HTML shell supports zh-Hant (default), en, and ja UI locales with a sidebar language switcher. Markdown body content remains in the extraction language.

Use references/html-documentation.md when changing the HTML documentation behavior.

9. Audit And Checkpoint

Run strict source, token, and component audits after an extraction or component expansion:

node <skill-root>/scripts/audit_sources.mjs <target-root> --strict
node <skill-root>/scripts/audit_tokens.mjs <target-root> --strict
node <skill-root>/scripts/audit_components.mjs <target-root> --strict

Use non-strict mode only for an empty starter package or early setup check.

Update design-system/SESSION_STATE.md with:

• completed outputs
• key decisions
• open questions
• token layers changed
• generated HTML docs path
• generated review queue path
• audit result
• source duplicate review result
• Figma MCP target coverage, including unresolved Figma targets
• component similarity review result
• recommended next prompt

Then stop and ask the user what to do next. Suggested choices:

• review and refine the extraction
• expand component tokens
• generate Figma Variables or token export
• create/update cross-agent instructions
• start a separate product implementation workspace

Post-Checkpoint Workflows

Component Expansion Pass

Use this pass when the user chooses to expand component tokens after the initial extraction.

1. Pick one or more planned components from design-system/COMPONENT_INVENTORY.md.
2. Confirm the component has evidence in design-system/DESIGN_EVIDENCE_MAP.md.
3. Create or update design-system/components/<component-name>.md from design-system/COMPONENT_SPEC_TEMPLATE.md.
4. Add missing system tokens only when they are reusable product-wide semantics.
5. Add component tokens in tokens/tokens-comp.css; component tokens must reference system tokens only.
6. Update COMPONENT_INVENTORY.md status and missing states.
7. Update related interaction and page composition rules.
8. Regenerate docs/design-system/index.html and docs/design-system/review.html.
9. Run node <skill-root>/scripts/audit_sources.mjs <target-root> --strict, node <skill-root>/scripts/audit_tokens.mjs <target-root> --strict, and node <skill-root>/scripts/audit_components.mjs <target-root> --strict.
10. Update SESSION_STATE.md, then stop and ask for the next step.

Gates

Evidence Gate

If an important design rule has no source evidence, mark it Low confidence or ask the user before making it normative.

Do not count duplicate screenshots, duplicate Figma nodes, or duplicate rendered routes as independent evidence until the duplicate source decision is recorded. If a source fingerprint matches or appears very close to another source, ask the developer for a reuse/ignore/keep-distinct decision before it changes confidence.

Token Gate

If a component needs a semantic or component token that does not exist, create or propose the token at the correct layer. Never use hardcoded fallback values in implementation guidance.

Do not silently merge or split close token values. When near duplicate colors or numbers are found, ask the developer for a merge/keep-distinct decision and document it before the checkpoint.

Do not silently create system/component token aliases that resolve to the same value in the same semantic audit group. If duplicate aliases are intentional, document why they must remain distinct.

Do not dedupe component tokens only because their reference values are close. Use the inheritance chain and usage fingerprint first; component tokens in different component categories or slots can stay distinct when their purpose differs.

Component Gate

Before adding a new component spec, check COMPONENT_INVENTORY.md and existing component docs. Reuse or extend a known component when intent, anatomy, slots, and states match.

Do not create a new component only because the Figma layer name is new. If a candidate resembles an existing component, present the visual comparison and fingerprint difference, then ask for a merge/variant/keep-distinct/block decision.

Strict component audit automatically compares component fingerprints. If it reports an automatic similarity candidate, resolve it in COMPONENT_INVENTORY.md before treating the extraction as complete.

Figma MCP Handoff Gate

When a source is Figma, do not mark the extraction ready for implementation until Figma source rows and affected component specs include either a usable Figma URL plus MCP target, or a documented reason why the target cannot be resolved. Downstream Storybook implementation depends on these traces to inspect the original node with Figma MCP before writing component code.

Implementation Boundary Gate

Do not generate product UI code, Storybook implementation code, or app routes inside this skill before the checkpoint unless the user explicitly requests product implementation.

Cross-Agent Use

If the user wants to use the extraction package with Claude Code, Cursor, or Codex, read references/agent-integration.md and generate the appropriate instruction files from the extracted rules. Keep agent instructions short and point them back to the design-system docs, token audit, and Figma MCP source traces.

Resource Map

• references/visual-analysis-rubric.md: how to analyze images, Figma, and rendered UI.
• references/token-architecture.md: token naming and inheritance rules.
• references/component-spec-rules.md: component anatomy, state, accessibility, and token spec rules.
• references/page-composition-rules.md: layout, density, page shell, and composition rules.
• references/anti-ai-style-rules.md: constraints that prevent generic AI-looking UI.
• references/agent-integration.md: Claude Code, Cursor, and Codex handoff guidance.
• references/html-documentation.md: static HTML documentation output rules.
• assets/design-system-template/: starter output package.
• scripts/audit_sources.mjs: source inventory and duplicate source review audit; pass --strict after real extraction work.
• scripts/audit_tokens.mjs: token layer audit; pass --strict after real extraction work.
• scripts/audit_components.mjs: component similarity review audit; pass --strict after inventory or component spec changes.
• scripts/generate_docs_html.mjs: generated developer-facing HTML docs, including design-system/components/*.md.
• scripts/generate_review_html.mjs: generated visual review queue for duplicate sources, near tokens, color scale issues, and similar components.