figma-write-to-figma
Skill0 starsChanged 5 months agoMITView on GitHub
Write designs into Figma files using the official Figma MCP server's generate_figma_design tool. Use this skill whenever the user wants to create designs in Figma, push UI into Figma, generate Figma frames from descriptions, capture web pages to Figma, or convert HTML/CSS to Figma design layers. Also use when the user says "write to Figma", "create in Figma", "push to Figma", "design in Figma", or provides a Figma URL and wants new designs created there. IMPORTANT — the Figma MCP is NOT read-only. It can write editable design layers to Figma files.
In this repository3 other files it gives its agents.
- design-explorerSkill
- obsidian-plugin-devSkill
- pareto-analysisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 11 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If generate_figma_design is not in the available tool list:
- Very specific: line 25
Run /mcp in Claude Code
- Distinctive: line 39
Create the design as local web pages.
- Distinctive: line 41
Use semantic HTML with clean CSS
- Distinctive: line 44
Create separate HTML pages for each frame/screen you want in Figma
- Distinctive: line 82
Start a local development server:
- Very specific: line 95
Verify it works: curl http://localhost:8765/
- Distinctive: line 99
Call the tool to capture the live UI into Figma:
- Distinctive: line 121
After capture, use the read tools to verify:
- Distinctive: line 129
Direction: Write to Figma
- Distinctive: line 164
Use flexbox/grid (maps to Figma Auto Layout)
- Distinctive: line 165
Avoid complex CSS transforms
- Distinctive: line 166
Use explicit sizing rather than intrinsic sizing
- Distinctive: line 167
Test at the exact resolution you want in Figma
≈ “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
Write Designs to Figma
Overview
The official Figma MCP server (https://mcp.figma.com/mcp) includes the generate_figma_design tool which writes editable design layers into Figma files. This is NOT a screenshot — it creates real, editable frames, text layers, shapes, and components.
Many Claude users incorrectly assume the Figma MCP is read-only. It is not. The generate_figma_design tool is the write mechanism.
Prerequisites
- Figma MCP plugin installed:
claude plugin install figma@claude-plugins-official - Figma MCP authenticated: The remote server at
https://mcp.figma.com/mcpmust be authenticated via OAuth - Figma seat: User needs a Full or Dev seat on a paid Figma plan (Professional, Organization, or Enterprise)
- Supported client: Currently Claude Code and Codex by OpenAI
Authentication
If generate_figma_design is not in the available tool list:
- Run
/mcpin Claude Code - Select the
figmaserver - Choose "Authenticate"
- Complete the OAuth flow in the browser
- Restart the Claude Code session — new MCP tools only load at session start
Check authentication status:
whoamitool returns the user's email, plans, and seat type- Auth cache at
~/.claude/mcp-needs-auth-cache.jsonshows servers needing auth
Workflow: Creating Designs in Figma
Step 1: Build the UI as HTML/CSS
Create the design as local web pages. This is the source material that gets converted to Figma layers.
- Use semantic HTML with clean CSS
- Load web fonts (Google Fonts for free fonts, or local fonts for commercial ones like Tiempos)
- Build at the target resolution (e.g., 1440×900 for desktop screens)
- Create separate HTML pages for each frame/screen you want in Figma
- CRITICAL: Include the Figma capture script in every HTML page's
<head>:
<script src="https://mcp.figma.com/mcp/html-to-design/capture.js" async></script>This script enables the capture toolbar that lets generate_figma_design convert DOM elements to Figma layers. Without it, the tool cannot capture the page.
Example structure:
my-design/
├── styles.css
├── colors.html → Color palette page
├── typography.html → Type samples
├── components.html → Buttons, forms, cards
├── dashboard.html → Full screen (1440×900)
└── detail.html → Full screen (1440×900)Example HTML template:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>My Design</title>
<link rel="stylesheet" href="styles.css">
<script src="https://mcp.figma.com/mcp/html-to-design/capture.js" async></script>
</head>
<body>
<!-- Your design here -->
</body>
</html>Step 2: Serve Locally
Start a local development server:
# Simple Python server
cd my-design && python3 -m http.server 8765
# Or use npx serve
npx serve my-design -p 8765
# Or use Vite for hot-reload
npx vite my-design --port 8765Verify it works: curl http://localhost:8765/
Step 3: Use generate_figma_design
Call the tool to capture the live UI into Figma:
To a new Figma file:
"Capture the UI at http://localhost:8765/dashboard.html into a new Figma file"
To an existing Figma file:
"Capture http://localhost:8765/dashboard.html to https://www.figma.com/design/[fileKey]/[fileName]"
Multiple pages:
"Capture all pages from http://localhost:8765 into my Figma file at [URL]. Start with colors.html, then typography.html, then components.html, then all screens."
Step 4: Capture Toolbar
When generate_figma_design runs:
- A browser window opens showing the localhost page
- A capture toolbar appears for selecting specific elements or pages
- The user selects what to capture (full page, specific elements, different states)
- The user signals when done
- The tool returns a link to the Figma file with the new design layers
Step 5: Verify and Iterate
After capture, use the read tools to verify:
get_screenshot— Visual check of the created framesget_metadata— Verify layer structure and namingget_design_context— Check the code representation matches
Tool Reference
generate_figma_design (WRITE)
- Direction: Write to Figma
- Server: Remote only (
https://mcp.figma.com/mcp) - What it does: Captures live UI from web apps/localhost and converts to editable Figma design layers
- Supported file types: Figma Design files
- Clients: Claude Code, Codex by OpenAI
Other Write Tools
| Tool | What it writes |
generate_diagram | Creates FigJam diagrams from Mermaid syntax |
add_code_connect_map | Maps Figma nodes to code components |
send_code_connect_mappings | Saves bulk Code Connect mappings |
Read Tools (for verification)
| Tool | What it reads |
get_design_context | Design data, code representation |
get_screenshot | Visual screenshot of a node |
get_metadata | XML structure with IDs, names, sizes |
get_variable_defs | Variables and styles |
whoami | User identity and plan info |
Common Issues
"generate_figma_design is not available"
The remote Figma MCP needs authentication. Run /mcp → select figma → Authenticate. Then restart the Claude Code session.
"User does not have permission"
The user needs a Full or Dev seat on a paid Figma plan. View-only or Collab seats cannot use this tool. Check with whoami.
"Font not rendering correctly"
Commercial fonts (Tiempos, Graphik, etc.) must be installed locally on the machine running the server. Google Fonts are loaded via @import or <link> tags.
Design looks different in Figma
The capture converts CSS to Figma's layout system. For best results:
- Use flexbox/grid (maps to Figma Auto Layout)
- Avoid complex CSS transforms
- Use explicit sizing rather than intrinsic sizing
- Test at the exact resolution you want in Figma
Examples
Example 1: Design system to Figma
User: "Create a design system for our app and put it in Figma"
1. Build HTML pages for colors, typography, components
2. Serve on localhost
3. generate_figma_design → capture each page
4. Result: Editable Figma file with design systemExample 2: Redesign existing app
User: "Redesign our dashboard and create it in Figma"
1. Screenshot existing app for reference
2. Build new dashboard design as HTML/CSS
3. Serve on localhost
4. generate_figma_design → capture to Figma
5. Result: New design in Figma for team reviewExample 3: Prototype from description
User: "Design a settings page with sidebar nav and put it in my Figma file"
1. Build settings page as HTML/CSS
2. Serve on localhost
3. generate_figma_design → capture to user's Figma URL
4. Result: Settings page as editable Figma layersDoes 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.

