figma-design-workflow

Retrieve structured Figma design context via the official Figma MCP for design-to-code implementation.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill figma-design-workflow-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-design-workflow
Source: https://github.com/marcmarti9/agentit/tree/main/skills/figma-design-workflow
Command: npx skills add https://github.com/marcmarti9/agentit --skill figma-design-workflow-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing UI from Figma often degrades into screenshot guessing, duplicated tokens, and lookalike components that ignore the design system. This Skill uses the official Figma MCP to pull structured design context—hierarchy, variables, components, Code Connect mappings, and assets—so implementations preserve actual design intent. ## Core Features & Use Cases - Design-to-code workflow: Resolve exact frames or selections, retrieve layout, spacing, typography, and variables, then build reusable components that match Figma semantics. - Design-system authority resolution: Decide whether Figma or code is the source of truth when they disagree, and report drift instead of inventing near-duplicate tokens. - Code-to-Figma writes: When the MCP seat allows, write native editable Figma structures and reuse existing components, styles, and variables. - Use Case: A developer receives a Figma handoff link for a new settings page. The Skill retrieves the exact frame's variables and Code Connect mappings, reuses the repository's existing tokens and components, and verifies the rendered result in the browser against the intended frame. ## Quick Start Use the Figma MCP to retrieve the design context for this Figma frame link and implement it as a component using our existing design tokens.

Frequently Asked Questions about figma-design-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a Figma design in code using MCP?▼

Connect the official Figma remote MCP at https://mcp.figma.com/mcp, then resolve the exact frame or selection rather than reading the whole file. Retrieve hierarchy, layout, variables, and components, check Code Connect mappings, and build the smallest reusable component structure that preserves Figma semantics.

How to set up the Figma MCP server in Claude Code or Codex?▼

In Claude Code run: claude mcp add --transport http figma https://mcp.figma.com/mcp. In Codex CLI run: codex mcp add figma --url https://mcp.figma.com/mcp. Authentication uses Figma's OAuth flow, and credentials should never be stored in the repository.

Can the Figma MCP write components back to Figma?▼

Write-to-canvas support depends on the user's Figma seat and the tools Figma exposes. When available, write native editable structures reusing existing components and variables, and avoid destructive rewrites of team-owned libraries. Read-only seats should be treated as a real constraint.

What should I do when Figma and code design tokens disagree?▼

First determine which side is authoritative for the project. If Figma is current, update the implementation; if code tokens are authoritative and Figma is stale, preserve code and report the drift. Never silently introduce near-duplicate colors, spacing, or components.

Why should I not convert every Figma group into a component?▼

Component boundaries should follow reusable behavior and semantics, not raw layer nesting. Converting every group creates overfitted, non-reusable components. Check Code Connect mappings and existing repository components before creating new ones.