claude2figma — Claude Code skill: what it does, how to install
claude2figma enforces design system tokens and master components when writing to Figma via Figma MCP. It validates style and variable bindings after every canvas edit.
MIT 210 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill claude2figma -a claude-codeWhat claude2figma does
This setup stops the agent from dumping raw hex values and detached frames into your designs. It forces every canvas operation through Figma MCP to pick master component instances, while tying color, typography, spacing and radii straight to existing variables and styles.
The package installs four focused skills: figma-preflight to check permissions and map tokens, reference-interpreter to turn visual inputs into a design brief, component-rules for Auto Layout structure, and figma-style-binding to confirm bindings right after writing.
Without an authenticated Figma MCP connection and an existing design system in your file, the workflow stops immediately.
What it helps with
- insert master component instances instead of detached frames
- bind colors, typography and radii to Figma variables
- verify token bindings right after updating canvas nodes
- parse visual references into a structured design brief
Example prompts for the agent
- Run the preflight check with claude2figma and load the token registry
- Build a settings modal following the component rules and design system
- Analyze this interface reference and write the brief before generating components
How to install claude2figma
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill claude2figma -a claude-code2Manually: put the files in place
~/.claude/skills/claude2figma/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/claude2figma/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill claude2figma -a codex2Manually: put the files in place
.agents/skills/claude2figma/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill claude2figma -a cursor2Manually: put the files in place
.cursor/skills/claude2figma/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/claude2figma2Manually: put the files in place
.github/skills/claude2figma/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill claude2figma -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/claude2figmaManually: put the files in place
.devin/skills/claude2figma/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill claude2figma -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about claude2figma
How to install claude2figma in Claude Code?
Run npx skills add podo/design-agent-skills --skill claude2figma -a claude-code in your terminal.
What does claude2figma do?
It enforces strict design system compliance by creating component instances and linking styles to Figma variables with post-write validation.
What prerequisites are needed to run it?
You need an active, authenticated Figma MCP server and a target Figma file that has a local or linked design system.
Source text
SKILL.md · MIT
--- name: claude2figma description: | Skill set that enforces design system compliance when Claude writes to Figma through the Figma MCP server: components are instances of master components, and colors/fonts/spacing/radii bind to Figma variables and styles instead of raw values. Every canvas write is followed by a binding check. Needs a Figma file with a design system and the Figma MCP server. triggers: - "claude2figma" - "Figma token compliance" - "Figma variables enforcement" - "design system Figma" - "senlindesign" - "Figma design system enforcement" das: type: package category: figma-code upstream: "https://github.com/senlindesign/claude2figma" version: latest install: false --- # claude2figma > Catalogue stub — full package: [senlindesign/claude2figma](https://github.com/senlindesign/claude2figma) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** This package installs 4 skills (`figma-preflight`, `component-rules`, `figma-style-binding`, `reference-interpreter`); checking the first. - Global: `f=~/.agents/skills/figma-preflight/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/figma-preflight/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `figma-preflight`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/claude2figma ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add senlindesign/claude2figma --skill figma-preflight component-rules figma-style-binding reference-interpreter -g -y ``` **Project:** ```bash npx skills add senlindesign/claude2figma --skill figma-preflight component-rules figma-style-binding reference-interpreter -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Claude Code plugin route:** ``` /plugin marketplace add senlindesign/claude2figma /plugin install claude2figma@claude2figma ``` **Heads-up** - **Requires:** Figma MCP server connected and authenticated; a Figma file with a Design System (local, or linked through a Library) - **License:** MIT <!-- das:install:end --> ## Invoke after install There is no skill called `claude2figma`; the package installs these skills, which work together: - Skill name: `figma-preflight` — say "let's start" with a Figma URL: runs the preflight check and loads the token map and component registry (start here) - Skill name: `reference-interpreter` — share a screenshot, URL or description and get a structured design brief before building - Skill name: `component-rules` — any UI construction task: library-first component lookup, Auto Layout, semantic naming - Skill name: `figma-style-binding` — any color, font or spacing operation: bind to variables and styles, then verify after the write - Trigger phrases: "claude2figma", "Figma token compliance", "Figma variables enforcement", "design system Figma" ## What it does An enforcement layer for building in Figma against an existing design system. A preflight step checks the MCP connection, file permissions, libraries, styles, variables and components, then every build follows one loop: search the design system, create instances of master components (not rebuilt or detached copies), bind all color, typography, spacing and radius values to variables and styles, and verify the bindings. The skills CLI installs only the skills. The upstream README also asks you to copy its `.claude/settings.json` (Figma tool permissions and a reminder hook) and `CLAUDE.md.template` (where you paste your Figma file URL) into your project. ## When NOT to use - Reading or auditing existing Figma designs — use `figma-official-skills` (Figma MCP) - Creating a design system from scratch, free-form design without a design system, or FigJam work - Code-to-design without a token-based design system - Token architecture outside Figma — use `design-tokens-skill`
© podo · MIT · podo/design-agent-skills