Figma Generate Design skill for Codex.
The figma-generate-design skill has Codex build or update full screens in Figma, such as pages, modals, drawers and panels, from code or a description. It reuses your published design system instead of drawing boxes with hex colors. It ships in the Figma plugin for Codex.
Updated November 12, 2026 · 3 min read
At a glance
| Skill name | figma-generate-design |
| Comes with | The Figma plugin, by Figma |
| Install | codex plugin add figma@openai-curated, or /plugins in Codex |
| Codex uses it | When you ask it to build or update a page, modal, dialog, drawer, sidebar or panel in Figma, from code or a description |
| Source | openai/plugins on GitHub |
What it does
The skill works with the figma-use skill from the same plugin, which holds the Plugin API rules. It needs the Figma MCP server and a target Figma file. If you don’t have a file yet, it creates one first.
Before it draws anything, Codex collects what your design system already has:
- Components: it checks Code Connect files in your codebase first, then the instances in existing screens, and only then searches the libraries.
- Variables and styles: colors, spacing and radii are bound to variables, and text and shadows use the file’s styles. No hard-coded hex values when a token exists.
- Font: it finds your product’s typeface in the source and doesn’t default to Inter. After building, it checks that the text really uses that font.
Then it creates one wrapper frame and builds the view one section per call. Repeated elements become local components, and icons are imported from your codebase’s SVGs. It takes a screenshot of each section to catch clipped text, placeholder labels and wrong variants.
For a web app with images, it also captures the running page with generate_figma_design. It matches that capture’s layout, copies its images across, and then deletes the capture.
When to use it
Use it when your team keeps a Figma design system and you want Codex’s screens to land in Figma as real component instances. The result stays linked to your library, so it updates when the components change.
Try it
Use the figma-generate-design skill. Build our pricing page from src/app/pricing in this Figma file: [Figma file URL]. Use our design system components and variables, and match the product font.
Does it work in Claude Code?
Only with the Figma MCP server connected. Every step calls its tools, such as use_figma, search_design_system and get_screenshot. With the server set up, copy this folder and the figma-use folder from GitHub into ~/.claude/skills, since the skill won’t run without figma-use.