Skip to main content
Agent skill

Design Extract

Extract design tokens (color / typography / spacing) from imported source code, screenshots, or Figma exports into the canonical token bag token-map consumes.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Design Extract when an AI agent needs a reusable SKILL.md workflow for this job: Extract design tokens (color / typography / spacing) from imported source code, screenshots, or Figma exports into the canonical token bag token-map consumes.

When not to use it

Skip Design Extract when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/design-extract
# Save SKILL.md to ~/.claude/skills/design-extract/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/design-extract/SKILL.md. For a shared project, commit the folder at .claude/skills/design-extract/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Design Extract skill for this task: Use Design Extract when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Design extract

Spec §10 / §21.3.2: tokens scattered across a repo's CSS / theme files / Tailwind config / styled-components helpers / SCSS partials need to be lifted into one bag before `token-map` can crosswalk them onto the active OD design system. This atom does the lifting; the input shape is intentionally generic so the same atom serves both code-migration and figma-migration when fed different sources.

## Inputs

- `code/index.json` from `code-import` (code-migration), OR - `figma/tree.json` from `figma-extract` (figma-migration), OR - A folder of screenshot images (tune-collab quick-tune flows).

## Output

```text project-cwd/ └── code/ └── tokens.json # { colors[], typography[], spacing[], radius[], shadow[] } ```

Each token entry carries:

```jsonc { "kind": "color", "name": "primary-500", // optional source name "value": "#5b8def", // canonical value "sources": ["styles/global.css:42", "tailwind.config.js:24"], "usage": ["Header.tsx", "Footer.tsx"] } ```

`sources[]` and `usage[]` are the audit trail `token-map.unmatched.json` references when a target token can't be found.

## Convergence

The atom completes when `code/tokens.json` exists. Empty token bags emit a warning event but do not abort — `token-map` handles the empty case by skipping its mapping pass.

## Anti-patterns the prompt fragment forbids

- Hard-coded hex values inside JSX literals (`color: '#fff'`) are tokens for this atom's purposes; record them with `kind:'color'` and a synthetic name so they don't disappear into the noise. - Tailwind utility scans must dedupe palette references against the active theme — never list `bg-blue-500` and `bg-blue-600` as one token.

## Status

Implemented by the daemon runner in `apps/daemon/src/plugins/atoms/design-extract.ts`. It scans the indexed source files, extracts CSS, Tailwind, and JavaScript token evidence, and writes `code/tokens.json`.

Intended uses

  • Use Design Extract when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.