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.

CodingPack: OpenAI skillslinkfigma
Author
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 pick figma.

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.

Open the source

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.

More from the pack OpenAI skills

ASP.NET Core apps

Guides the agent through current ASP.NET Core practice: choosing Blazor, Razor Pages, MVC or Minimal APIs, Program.cs and middleware order, auth, EF Core, tests and upgrades to .NET 10. Use when building, reviewing or upgrading an ASP.NET Core app.

ChatGPT Apps SDK

Builds ChatGPT apps on the Apps SDK: reads current OpenAI docs first, picks an app archetype, plans MCP tools, adapts an official example or scaffolds a Node server and widget, then tests in Developer Mode. Use when building or fixing an app inside ChatGPT.

CLI creator from API docs

Builds a durable CLI from API docs, an OpenAPI spec, curls or a script: JSON output, doctor and dry-run commands, safe auth, installed on PATH and paired with a companion skill. Use when an agent keeps hitting the same service through ad hoc calls.

Define a measurable goal

Turns a fuzzy intention into one measurable goal with a validator, scope and stop condition, then registers it via get_goal and create_goal. Use before goal-backed or long-running agent work, when "done" needs a number or a check.

Address GitHub PR comments

Fetches all comments, reviews and inline threads on the current branch's GitHub PR with a gh GraphQL script, numbers them and fixes only the ones you pick. Use when a PR has review comments to work through and you want to choose which get changed.

Fix failing GitHub Actions checks

Finds failing GitHub Actions checks on a PR with gh, pulls the logs, extracts the failure snippet and drafts a fix plan, changing code only after approval. Use when a PR's CI is red and you want the cause and a plan before any edit.

Jupyter notebooks

Creates and tidies Jupyter notebooks for experiments or tutorials from bundled templates via a stdlib script, with structure patterns and a run-top-to-bottom checklist. Use when starting a notebook or turning a messy one into something others can rerun.

Linear issues and projects

Works with Linear issues, projects and cycles through Linear's MCP server in a fixed order: setup, scope, read, then write, with sample workflows for triage, sprints and releases. Use when an agent should read or update Linear as part of a task.

Deploy to Netlify

Deploys the current project to Netlify with `npx netlify`: checks the login, links the folder to a site by Git remote or creates one, builds locally and returns a preview or production URL. Use when you want to publish a site to Netlify from your machine.

Browser automation with Playwright CLI

Drives a real browser from the terminal with playwright-cli: snapshots give element refs for clicks and typing, plus screenshots, console, network and traces, with no test files written. Use when a task needs a browser clicked through step by step.

Deploy to Render

Deploys an app to Render from a Git repo: writes and validates a render.yaml Blueprint with services, databases and secrets, or creates one service through the Render MCP server, then checks status and logs. Use when an app needs hosting on Render.

Security best-practice review

Checks Python, JavaScript/TypeScript and Go code against bundled security specs for ten frameworks, writes a report by severity with line numbers and fixes one finding at a time. Use when you explicitly ask for a security best-practice review.

Repository threat model

Writes a repository-grounded threat model: trust boundaries, assets, attacker capabilities and ranked abuse paths with mitigations, asking you to confirm key assumptions before the final file. Use when you explicitly ask to threat model a codebase.

Sentry issues and events

Reads Sentry issues and events through the sentry CLI without changing anything: recent production errors, issue and event details, AI root-cause summaries, with PII redacted. Use when you ask what is failing in production according to Sentry.

Deploy to Vercel

Deploys a project to Vercel, as a preview unless told otherwise, through the Vercel CLI or, without an account, a bundled script that uploads the folder and returns a preview link and a claim link. Use when you want a shareable deployment link fast.

Figma use_figma prerequisite

Sets the rules an agent must load before every use_figma call that runs Plugin API JavaScript in a Figma file: return values, page resets, colours, fonts, node IDs, small validated steps. Use when creating or editing anything inside a Figma file.

Implement a Figma design in code

Implements a Figma frame or component as code in your repo with 1:1 visual parity: fetches context and a screenshot, maps the output to project tokens and components, then runs a validation checklist. Use when a Figma link must become production UI.

Generate a Figma design from an app

Builds or updates a full screen in Figma from code or a description, section by section, using the file's published components, variables and styles instead of hardcoded values. Use when a page from your app should exist as a Figma screen.

Figma design system from a codebase

Builds a Figma design system library from a codebase in five supervised phases: discovery, variables and styles, page structure, components one by one, QA. Use when a product needs a Figma library that matches its code tokens and components.

Figma Code Connect components

Links published Figma components to the code components that implement them via Code Connect: finds unmapped ones, matches them in the codebase, maps only what the user approves. Use when a Figma library and its code both exist but are not linked.

Figma design system rules

Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.

Create a new Figma file

Creates a blank Figma design file or FigJam board in your drafts, resolving the plan through whoami, and returns the file key and URL. Use when the next Figma step needs a fresh file to write into.