token-map
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Profile →npx skills add nexu-io/open-design --skill token-map --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Token map Spec §10 / §21.3.1: every figma-migration / code-migration run crosses the same boundary — "the source has its own tokens; the target uses the active OD design system; we need a deterministic mapping". This atom produces that mapping. ## Inputs - `figma/tokens.json` from `figma-extract` (figma-migration), OR - `code/tokens.json` from `design-extract` (code-migration). - The active design system DESIGN.md (already injected into the prompt; the atom reads from the staged design-system context). ## Output ```text project-cwd/ └── token-map/ ├── colors.json # { source: '#hex' | 'tokenName', target: '--ds-token' }[] ├── typography.json # font + size + weight pairings ├── spacing.json # spacing scale crosswalk ├── unmatched.json # { source: ..., reason: 'no-target-equivalent' }[] └── meta.json # { sourceKind: 'figma' | 'code', generatedAt, atomDigest } ``` `unmatched.json` is the audit list a human reviews; the agent must not invent target tokens silently. ## Semantic token inference Figma often exports anonymous source names such as `color-3`, `paint/17`, or raw `#5B8DEF`. Do not ask the user to rename those before mapping. First infer the semantic role from usage evidence:
- Inputs
- Output
- Semantic token inference
- Before / after expectation
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the token-map skill do?
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
How do I install it?
Run `npx skills add nexu-io/open-design --skill token-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.