figma-implement-design
- Use it when:
- You have a link to a Figma frame or component and want it built in your codebase to match the design.
- It does:
- Fetches the node's design context, a screenshot and its assets through the Figma MCP server, then rewrites Figma's React and Tailwind output in your project's conventions.
- You get:
- Components that reuse or extend your existing ones and use your tokens, validated against the screenshot for layout, type, color, states, responsiveness, assets and accessibility.
- When they conflict:
- Your design-system tokens win over raw Figma values, with spacing or sizes adjusted minimally to keep the look, and deviations explained in code comments.
- Not for:
- Editing the Figma file itself, building screens in Figma or writing Code Connect mappings: it sends those to the repo's other Figma skills.
Needs the Figma MCP server connected and access to the Figma file; with the figma-desktop server, the Figma desktop app open with a node selected.
TL;DR
A design-to-code workflow from OpenAI's catalog of Codex skills, built on the Figma MCP server. From a Figma URL the agent extracts the file key and node ID; with the figma-desktop server it uses the node selected in the open file instead. It fetches the node's structured design context (layout, typography, colors, tokens, variants, spacing), falling back to a metadata map and child-by-child fetches when the response is too large, then a screenshot that stays the source of truth throughout. Images and SVGs come from the server's localhost asset endpoint: no new icon packages, no placeholders. Figma's output, usually React with Tailwind, is treated as a description of design and behavior, not as code to keep: the agent reuses your existing components, extending one rather than duplicating it, maps Figma values to your color, type and spacing tokens, and follows your routing, state and data-fetching patterns. New components get typed props and JSDoc comments. Before finishing it validates against the screenshot, including hover, active and disabled states, responsive constraints and WCAG accessibility. The openai/skills repository is marked deprecated; its README points to openai/plugins for current Codex skills.
Summarizes the skill at 49f948f.
npx skills add https://github.com/openai/skills --skill figma-implement-design skills.sh pageSource on GitHubAll skills from openai/skills
- Total Downloads
- 7,000 on skills.sh, Nov 9, 2026
- Repo stars
- 28,602 openai/skills
- First seen
- Feb 1, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 202 |
| Sep 28 | 179 |
| Oct 5 | 237 |
| Oct 12 | 134 |
| Oct 19 | 145 |
| Oct 26 | 143 |
| Nov 2 | 148 |
| Nov 9 | 114 |
| Category |
Taste for interfaces that don't look generated: direction, motion and accessibility. Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Needs an MCP server connected. An account, API key or paid plan with an outside service. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
No copy of its SKILL.md yet.