figma-manage-variables
Create, update, rename, delete, and organize Figma variables, collections, and modes — including fast batch create/update, setting scopes, code syntax, and adding theme modes. Use for incremental variable work: triggers 'create a variable', 'batch update variables', 'add a dark mode to my collection', 'rename this variable', 'set variable scopes', 'delete a variable/collection', 'add a mode'. Works on ANY Figma plan. For a from-scratch system use figma-setup-design-tokens; for code↔Figma sync use figma-import-tokens / figma-export-tokens.
npx skills add southleft/figma-console-mcp-skills --skill figma-manage-variables --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.
# figma-manage-variables — variable / collection / mode CRUD Incremental, surgical edits to a Figma variable system: create one or many, update values in bulk, rename, set scopes and code syntax, add/rename modes, and delete. All via `use_figma`, on any plan. ## Skill boundaries - **`use_figma` rules** — load the official **`figma-use`** skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level `await` + `return` (no IIFE, no `figma.closePlugin()`; `console.log` is not returned), inputs inlined as `const` at 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). - From-scratch bootstrap → `figma-setup-design-tokens`. Code sync → `figma-import-tokens` / `figma-export-tokens`. ## Workflow 1. **Identify targets.** Most ops need IDs. Get `variableId`/`modeId`/`collectionId` from the `figma-export-tokens` read script or `get_variable_defs`. Collections can also be looked up by name inside the script. 2. **Pick the operation** from [references/variable-ops.md](references/variable-ops.md) — i
- Skill boundaries
- Workflow
- Key rules
What does the figma-manage-variables skill do?
Create, update, rename, delete, and organize Figma variables, collections, and modes — including fast batch create/update, setting scopes, code syntax, and adding theme modes. Use for incremental variable work: triggers 'create a variable', 'batch update variables', 'add a dark mode to my collection', 'rename this variable', 'set variable scopes', 'delete a variable/collection', 'add a mode'. Works on ANY Figma plan. For a from-scratch system use figma-setup-design-tokens; for code↔Figma sync use figma-import-tokens / figma-export-tokens.
How do I install it?
Run `npx skills add southleft/figma-console-mcp-skills --skill figma-manage-variables --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 southleft/figma-console-mcp-skills, a repository with 67 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.