claude2figma — Claude Code plugin: features and install
claude2figma helps Claude Code build Figma screens from an existing design system and check that visual properties stay linked to its tokens.
MIT ★ 208 updated 2026-05-13
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude2figma@claude-communityWhat claude2figma does
claude2figma adds four skills for Claude Code and Figma: preflight checks, library component lookup, style binding, and reference interpretation. Before creating nodes, preflight checks the MCP connection, file permissions, libraries, styles, variables, and components in parallel. It then prepares a token map and component registry.
For each UI task, the agent searches the connected library, creates component instances, and binds colors, typography, spacing, and corner radii to Variables and Styles. A QA check runs after each Figma write. A screenshot, URL, or written reference can first be turned into a structured Design Brief.
You need Claude Code, an installed and authenticated Figma MCP Server, and a Figma file that contains a local or linked design system. Without the Figma MCP Server, the plugin cannot perform Figma operations.
What it helps with
- build a page from an existing design system
- bind colors and typography to Variables and Styles
- check Figma output after each write
- turn a screenshot into a structured Design Brief
Example prompts for the agent
- Start with preflight and check the Figma connection before building the screen.
- Build a login page, look up the form components in the library, and bind every visual value to a token.
- Turn this screenshot into a Design Brief, then build the section in Figma and run QA.
How to install claude2figma
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install claude2figma@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about claude2figma
How do I install claude2figma in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin with /plugin install claude2figma@claude-community.
What does claude2figma do?
It guides Claude Code to build Figma designs from an existing component library and design-token system. The plugin checks visual bindings after writing to Figma.
What does claude2figma require?
You need Claude Code, an installed and authenticated Figma MCP Server, and a Figma file with a local or linked design system.
Source text
SKILL.md · MIT
# Claude Code to Figma
[](https://docs.anthropic.com/en/docs/claude-code)
[](https://www.npmjs.com/package/@anthropic-ai/figma-mcp)
[](LICENSE)
Design System compliance for AI-generated Figma designs. 4 skills, 3-step preflight, zero raw values.
> **Quick start:** Clone, copy skills to `.claude/skills/`, paste your Figma URL into `CLAUDE.md`, say "let's start". [Full install guide below.](#installation)
[Chinese / 中文版](README.zh-CN.md)
---
## Why?
AI can write to Figma now. But without guidance, it builds everything from scratch — hardcoded hex colors, arbitrary font sizes, raw spacing values. The result looks right but is completely disconnected from your Design System. Every color is a magic number. Every component is a one-off. Your design tokens might as well not exist.
cc2figma fixes this with 4 Claude Code Skills that enforce Design System compliance at every step:
- Components are Instances of your Master Components, not rebuilt from scratch
- Colors, fonts, spacing, and radii bind to Variables and Styles, not raw values
- Every write to Figma is automatically verified for token compliance
---
## Before & After

> **With Skills:** Master Component Instances, all visual values bound to Design System Variables and Styles.
> **Without Skills:** Hardcoded colors, arbitrary spacing, components built from scratch — looks right, but zero Design System connection.
---
## Preflight System
Before every design session, a 3-step parallel check ensures everything is connected:

MCP connection, file permissions, libraries, styles, variables, and components — all verified in parallel before a single node is created.
---
## Usage Examples
Say "let's start" to run preflight, then describe what you want:
You: Build a login page with email and password fields
Claude: [searches DS for Form, Input, Button components]
[creates Instances, binds all tokens]
[takes screenshot for verification]
You: Add a registration form next to it with a confirm password field
Claude: [reuses same DS components, adds new section]
[QA verifies all bindings automatically]
You: Here's a screenshot of the dashboard we need
Claude: [analyzes reference, outputs structured Design Brief]
[builds section by section, verifying after each step]
Every interaction follows the same loop: **search DS** → **create Instances** → **bind tokens** → **verify**.
---
## What's Included
### 4 Skills
| Skill | Trigger | What it does |
| ----- | ------- | ------------ |
| `figma-preflight` | "let's start", first Figma URL | 3-step parallel check + Token Map + Component Registry |
| `component-rules` | Any UI construction task | Library-first lookup, Auto Layout, semantic naming |
| `figma-style-binding` | Any color, font, or spacing operation | Enforce Variable / Style binding + post-write QA verification |
| `reference-interpreter` | Share screenshot, URL, or description | Output structured Design Brief before building |
### How They Work Together
"let's start"
|
v
① preflight ─── one-time setup, load Token Map + Component Registry
|
v
② reference-interpreter ─── optional: screenshot / reference → Design Brief → user confirms
|
v
┌→ ③ component-rules ─── search Library, use Instances
│ |
│ ④ figma-style-binding ─── bind every value to a token, then auto-verify
│ |
└── next section (loop until done)
---
## Good For / Not For
| Good For | Not For |
| -------- | ------- |
| Building pages from an existing Design System | Creating a Design System from scratch |
| Describing UI in natural language, Claude builds it in Figma | Pixel-perfect illustration or icon drawing |
| Working in a DS file or a file with a linked DS library | Free-form design without a Design System |
| Ensuring 100% token compliance in design output | FigJam / whiteboard workflows |
---
## Installation
### Prerequisites
- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) (CLI / Desktop / VS Code)
- [Figma MCP Server](https://www.npmjs.com/package/@anthropic-ai/figma-mcp) installed and authenticated
- A Figma file with a Design System (locally defined or linked via Library)
### Install
```bash
# 1. Clone the repo
git clone https://github.com/senlindesign/cc2figma.git
# 2. Copy skills to your project
cp -r cc2figma/.claude/skills/* your-project/.claude/skills/
# 3. Copy config
cp cc2figma/.claude/settings.json your-project/.claude/settings.json
# 4. Copy CLAUDE.md template
cp cc2figma/CLAUDE.md.template your-project/CLAUDE.md
```
### Configure CLAUDE.md
Open `CLAUDE.md` and paste your Figma file URL:
```markdown
# Figma Design Project
- **Figma file:** <https://www.figma.com/design/YOUR_FILE_KEY/...>
- **Fonts:** [leave blank — Preflight auto-detects from your DS]
- **Session goal:** [what are we designing today?]
## Rules
1. Every visual value must bind to a Style or Variable.
2. Always search connected libraries before building any component from scratch.
3. Never start designing before the Design Brief is confirmed.
```
Then say "let's start" in Claude Code. Preflight handles the rest.
---
## Supported Scenarios
| Scenario | How It Works |
| -------- | ------------ |
| **Working in a DS file directly** | Preflight reads all local Styles, Variables, and Components. Full token binding. |
| **New file with a linked DS library** | Component Instances inherit all token bindings from masters automatically. Library variables can be imported for new frames. |
---
## Directory Structure
```
your-project/
├── CLAUDE.md # Project config (Figma URL, fonts, rules)
└── .claude/
├── settings.json # Permissions + QA Hook
└── skills/
├── figma-preflight/ # 3-step parallel check + Token Map + Component Registry
├── component-rules/ # Library-first, Auto Layout, naming
├── figma-style-binding/ # Color / Text / Spacing binding + QA verification
└── reference-interpreter/ # Reference → Design Brief
```
---
## Known Limitations
| Limitation | Workaround |
| ---------- | ---------- |
| Doubly-nested Instances can't be directly modified | `detachInstance()` on the outer instance first |
| `getLocalVariablesAsync()` can't see library variables | Instances inherit tokens automatically; use `importVariableByKeyAsync` for new frames |
| Invalid variant values in `setProperties` roll back the entire script | Read `componentPropertyDefinitions` to confirm valid values first |
---
## Contributing
Issues and PRs are welcome. If you have a Figma design workflow that could benefit from a new Skill, describe it in an Issue.
---
MIT © 2025 Sen Lin
© senlindesign · MIT · senlindesign/claude2figma