Curated

Skill 13 of 44

Figma

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code.

2 minutes · 427 words · 7 sections

Install

$ npx skills add openai/skills --skill figma

$ npx skills add openai/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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)

Run get_design_context first to fetch the structured representation for the exact node(s).
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.
Run get_screenshot for a visual reference of the node variant being implemented.
Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.
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.
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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/openai/skills, branch main, last pushed 8 September 2026.

Licence

Discovery

44 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: skills/.curated/*/SKILL.md, skills/.system/*/SKILL.md.

Issue colours

Resolved from a curated brand profile — hue 170°, chroma 0.124. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /openai/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.

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

Run get_design_context first to fetch the structured representation for the exact node(s).

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.

Run get_screenshot for a visual reference of the node variant being implemented.

Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.

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.

Validate against Figma for 1:1 look and behavior before marking complete.

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.

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.

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/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.

Figma

Figma MCP

Figma MCP Integration Rules

Required flow (do not skip)

Implementation rules

Asset handling

Link-based prompting

References

About this skill

Trigger

Colophon

Figma

Figma MCP

Figma MCP Integration Rules

Required flow (do not skip)

Implementation rules

Asset handling

Link-based prompting

References

Appendix 13.1–13.6

ReferencesMarkdown · 2 files

Assets3 files

Also bundled2 files

About this skill

Trigger

Colophon

Appendix 13.1–13.6

ReferencesMarkdown · 2 files

Assets3 files

Also bundled2 files