skilld
All skills
openai avatar

/figma

@dad3072 official
by openaiopenai/skills28k stars
1,891

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/figma

This session only. Nothing lands on disk.

SKILL.md

≈69 tokens always: the name and description. ≈717 when used: this file. ≈1.4k more on demand in 3 files.

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.

Source: SKILL.md on GitHub

Third-party checks

2 warnings17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill facilitates integration with Figma to assist with design-to-code workflows. It includes some standard security considerations such as interaction with an external service and guidance on environment variable configuration, which are consistent with its intended use as a developer tool.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    5/5 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at dad3072. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 8 months ago

Topics

README badge

README badge for openai/skills/figma

What it does

Fetches design context, screenshots, variables, and assets from Figma using the MCP server, then translates Figma nodes into production code while respecting the project's design system tokens and component conventions. Requires the Figma MCP server setup and is triggered by Figma URLs, node IDs, or design-to-code tasks.

Generated from the current SKILL.md.

Frequently asked

What Figma MCP tools does this skill use?
The skill uses get_design_context to fetch structured node data, get_metadata for high-level node maps, get_screenshot for visual references, and an assets endpoint to serve images and SVGs directly from Figma.
Do I need to set up environment variables or config to use this skill?
Yes. See references/figma-mcp-config.md for setup instructions, environment variables, and verification steps.
Can I use Figma design tokens and colors directly in my code?
The skill translates Figma output to React + Tailwind but requires you to replace those utilities with your project's design-system tokens, color system, and typography scale instead of using Figma's raw values.
What should I do if Figma assets are served as localhost URLs?
Use the localhost source directly in your code. Do not create placeholders, import new icon packages, or fetch from elsewhere — the MCP server is providing the asset for you.
Do I need to paste Figma links or node IDs to use this skill?
Yes. The skill is link-based: copy the exact Figma frame or layer link pointing to the node you want implemented and provide that URL to the MCP client.

Generated from the current SKILL.md. These answers refresh after source changes.