Figma MCP design context
Reads Figma frames through the Figma MCP server in a fixed order (design context, metadata, screenshot) and rebuilds them with the project's components and tokens; also covers server setup in Codex. Use when connecting Figma MCP or coding from a frame link.
figma- Author
- OpenAI
- Source
- openai/skills/skills/.curated/figma @ 49f948f
- License
- Figma Developer Terms
About this skill
What it does
This is the read side of OpenAI's eight Figma skills: it pulls a design through Figma's MCP server and turns it into code in your project. The order of calls is fixed: get_design_context for the exact node, get_metadata first when that response is truncated, then get_screenshot as the visual reference, then assets and code. The server's React and Tailwind output counts as a description, not code to paste: the agent swaps in the project's components and tokens and checks the result against the screenshot. Assets come from the server's localhost endpoint, never from new icon packages or placeholders.
Its two reference files also make it the setup skill of the set. references/figma-mcp-config.md registers the remote server in ~/.codex/config.toml (https://mcp.figma.com/mcp, a bearer token from FIGMA_OAUTH_TOKEN, an X-Figma-Region header, rmcp_client on) and covers token and OAuth errors. references/figma-tools-and-prompts.md lists eleven of the server's tools with sample prompts.
When to use it, and when not
Use it to connect the Figma MCP server, to look up which tool returns what, or for a quick design-to-code task from a frame link. The server takes the node ID from the link without opening the page, so it must point at the exact frame or layer.
For a larger build with a validation checklist, Implement a Figma design in code has the full procedure. Writing into a Figma file starts with Figma use_figma prerequisite.
How to run it
We do not copy this skill: its files fall under Figma's Developer Terms, not an open licence. Install it from the author's repository with the button to the source. In Codex the route is $skill-installer figma; for another agent, copy the figma folder into its skills directory. OpenAI has marked openai/skills deprecated. The Figma plugin in openai/plugins has no skill by this name: it connects the MCP server itself and handles design-to-code with figma-design-to-code. It needs a Figma account and a connected Figma MCP server; the setup notes cover Codex only.
- Claude Code:
/figma, or ask for the skill by name. - Codex:
$figma. - Cursor: type
/in the Agent chat and pickfigma.
Example: /figma Implement this frame with our components from src/ui: https://figma.com/design/<fileKey>/Checkout?node-id=12-34
How it differs from similar skills
Implement a Figma design in code runs the same calls as a seven-step workflow with a checklist and examples; this skill is the short rule set plus setup and the tool list. Figma design system rules writes such rules into your CLAUDE.md or AGENTS.md, so they apply without a skill. Distinctive frontend design invents a look when there is no design file.
Install
This skill is not copied to the catalog: its licence does not allow it. Install it from the author's repository.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel