SkillRepo
Sign InSign Up
Catalog
openai/figma

openai

figma

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

global
0installs0uses—~784
v1.1Saved Apr 20, 2026

Figma MCP

Use the Figma MCP server for Figma-driven implementation. For setup and debugging details (env vars, config, verification), see references/figma-mcp-config.md.

Figma MCP Integration Rules

These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.

Required flow (do not skip)

  1. Run get_design_context first to fetch the structured representation for the exact node(s).
  2. If the response is too large or truncated, run get_metadata to get the high-level node map and then re-fetch only the required node(s) with get_design_context.
  3. Run get_screenshot for a visual reference of the node variant being implemented.
  4. Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.
  5. Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible.
  6. Validate against Figma for 1:1 look and behavior before marking complete.

Implementation rules

  • Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style.
  • Replace Tailwind utility classes with the project's preferred utilities/design-system tokens when applicable.
  • Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
  • Use the project's color system, typography scale, and spacing tokens consistently.
  • Respect existing routing, state management, and data-fetch patterns already adopted in the repo.
  • Strive for 1:1 visual parity with the Figma design. When conflicts arise, prefer design-system tokens and adjust spacing or sizes minimally to match visuals.
  • Validate the final UI against the Figma screenshot for both look and behavior.

Asset handling

  • The Figma MCP Server provides an assets endpoint which can serve image and SVG assets.
  • IMPORTANT: If the Figma MCP Server returns a localhost source for an image or an SVG, use that image or SVG source directly.
  • IMPORTANT: DO NOT import/add new icon packages, all the assets should be in the Figma payload.
  • IMPORTANT: do NOT use or create placeholders if a localhost source is provided.

Link-based prompting

  • The server is link-based: copy the Figma frame/layer link and give that URL to the MCP client when asking for implementation help.
  • The client cannot browse the URL but extracts the node ID from the link; always ensure the link points to the exact node/variant you want.

References

  • references/figma-mcp-config.md — setup, verification, troubleshooting, and link-based usage reminders.
  • references/figma-tools-and-prompts.md — tool catalog and prompt patterns for selecting frameworks/components and fetching metadata.
Files7
7 files · 9.3 KB

Select a file to preview

Overall Score

86/100

Grade

A

Excellent

Safety

90

Quality

88

Clarity

84

Completeness

82

Summary

A skill for using the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, then translate Figma designs into production code. It enforces a structured workflow (design context → screenshot → asset download → implementation) and provides rules for respecting project conventions, design systems, and component reuse.

Detected Capabilities

Fetch structured design data from Figma via MCPRetrieve screenshots of Figma selectionsExtract variables, styles, and color tokens from designsDownload assets (images, SVGs) from FigmaTranslate Figma design output into project-specific codeMap Figma nodes to code components via Code ConnectGenerate design-system rules and token guidance

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

figma design to codetranslate figma frameimplement from figmafigma screenshotdesign system tokensfigma component mapping

Risk Signals

INFO

Bearer token authentication via environment variable (FIGMA_OAUTH_TOKEN)

references/figma-mcp-config.md
INFO

Network request to external MCP server (mcp.figma.com)

agents/openai.yaml, references/figma-mcp-config.md
INFO

Asset downloads from Figma MCP endpoint (localhost or remote)

SKILL.md, Asset handling section

Referenced Domains

External domains referenced in skill content, detected by static analysis.

mcp.figma.comwww.figma.com

Use Cases

  • Implement a UI component from a Figma design
  • Translate a Figma frame into React + Tailwind code
  • Extract variables and styles from Figma designs
  • Map Figma nodes to existing project components
  • Validate implemented UI against Figma for visual parity

Quality Notes

  • Strength: Clear, prescriptive workflow (get_design_context → get_metadata → get_screenshot) minimizes ambiguity and prevents truncation issues.
  • Strength: Implementation rules explicitly prioritize project conventions over raw Figma output, reducing misalignment between design and code.
  • Strength: Asset handling explicitly warns against creating placeholders and icon packages, enforcing proper design-system usage.
  • Strength: Link-based prompting pattern clearly explains how to extract node IDs and when to use frame/layer URLs.
  • Strength: References are well-organized and provide practical setup, troubleshooting, and prompt pattern examples.
  • Strength: Comprehensive tool catalog in figma-tools-and-prompts.md with clear use-case guidance for each tool.
  • Minor observation: The skill assumes Codex/RMCP client environment; portability to other agent platforms is unclear but documented via config reference.
  • Minor observation: Error handling for truncated responses is mentioned (use get_metadata first) but could be more explicit about fallback strategies.
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

Seeded from github.com/openai/skills

2026-03-16

Add openai/figma to your library

Get Started Free

Command Palette

Search for a command to run...