figma-setup-design-tokens
Skill83 starsChanged 6 months agoMITView on GitHub
Bootstrap a complete design-token system in Figma in one atomic step — create a variable collection, its modes (e.g. Light/Dark), and every variable with per-mode values together. Use when starting a token system from scratch: triggers 'set up design tokens in Figma', 'create a token collection with light and dark modes', 'scaffold variables', 'bootstrap a Figma theme'. Works on ANY Figma plan. For incremental edits to an existing system use figma-manage-variables; for syncing from a code tokens file use figma-import-tokens.
In this repository22 other files it gives its agents.
- figjam-create-contentSkill
- figma-analyze-component-setSkill
- figma-annotationsSkill
- figma-arrange-component-setSkill
- figma-audit-accessibilitySkill
- figma-blame-nodeSkill
- figma-check-design-paritySkill
- figma-commentsSkill
- figma-component-propertiesSkill
- figma-deep-componentSkill
- figma-design-system-inventorySkill
- figma-export-tokensSkill
- figma-extract-design-systemSkill
- figma-generate-changelogSkill
- figma-generate-component-docSkill
- figma-import-tokensSkill
- figma-library-variablesSkill
- figma-lint-designSkill
- figma-manage-variablesSkill
- figma-scan-code-accessibilitySkill
- figma-slidesSkill
- figma-version-historySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Create a variable collection + modes + all variables in a single use_figma call.
- Very specific: line 31
Two-tier systems: create *primitives* (raw values) with this skill, then create *semantic* tokens that alias them using figma-import-tokens …
- Distinctive: line 37
Keep one bootstrap per collection.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
figma-setup-design-tokens — atomic token-system bootstrap
Create a variable collection + modes + all variables in a single use_figma call. This is the
fastest way to stand up a new token system (or a new collection within one). Because it runs as one
atomic script, either everything is created or nothing is (failed scripts apply no changes).
Skill boundaries
use_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat the top of each script, colors in 0–1 range, load fonts before any text op,await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).- Incremental CRUD / batch edits to an existing system →
figma-manage-variables. - Sync from a code token file →
figma-import-tokens.
Workflow
- Agree the v1 scope. List the collection name, the modes (first one is the default), and the full token set with per-mode values. Lock this before writing — it's much cheaper than editing afterward.
- Fill the constants in
scripts/setup-tokens.js:COLLECTION_NAME,MODES,TOKENS(values keyed by mode name), and optional per-variableSCOPES. - Run via
use_figma(skillNames: "figma-setup-design-tokens"). It returns{ collectionId, modes, created, errors }. - Validate with
get_variable_defsor thefigma-export-tokensread script, then screenshot if you also created swatches.
Notes
- Two-tier systems: create primitives (raw values) with this skill, then create semantic
tokens that alias them using
figma-import-tokens(which has the alias pass) orfigma-manage-variables. Keep primitives single-mode and put theming on the semantic layer. - Set scopes: the default
ALL_SCOPESclutters every property picker. PassSCOPESfor the surfaces each token belongs to (FRAME_FILL/SHAPE_FILLfor backgrounds,TEXT_FILLfor text,GAPfor spacing,CORNER_RADIUSfor radii,WIDTH_HEIGHTfor sizing). - Keep one bootstrap per collection. Multiple collections = multiple runs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

