Figma Code Connect skill for Codex.
The figma-code-connect skill has Codex write Code Connect templates, the files that tell Figma which code component matches each design component. Give it a Figma URL and it finds the matching component in your repo and writes the mapping. It ships in the Figma plugin for Codex.
Updated November 12, 2026 · 3 min read
At a glance
| Skill name | figma-code-connect |
| Comes with | The Figma plugin, by Figma |
| Install | codex plugin add figma@openai-curated, or /plugins in Codex |
| Codex uses it | When you mention Code Connect or mapping Figma components to code, or ask to create or update .figma.ts files |
| Source | openai/plugins on GitHub |
What it does
The skill writes one kind of file: a ComponentName.figma.ts template that uses the figma.code`...` tagged template. It never writes .figma.tsx files or uses figma.connect(), the older parser-based format. If a .figma.tsx file already exists, it leaves it alone and adds the template next to it.
For each Figma URL, Codex follows the same steps:
- Asks the Figma MCP server which published components in the selection aren’t mapped yet.
- Reads each component’s properties: text, booleans, variants, instance swaps and slots.
- Searches your codebase for the matching component, using
figma.config.jsonpaths, and confirms the match with you. - Writes the template, mapping each Figma property to a real prop.
- Reads the file back and checks it.
It follows strict rules: every variant value gets mapped, so none render as undefined. Nested icons and children resolve dynamically instead of being hard-coded. And it never invents a prop the code component doesn’t have.
When to use it
Use it when your team publishes components to a Figma library and wants Dev Mode to show your real code. There are limits: Code Connect needs an Organization or Enterprise plan, the components must be published to a team library, and the URL must include a node-id.
Try it
Use the figma-code-connect skill. Create a Code Connect template for the Button in this Figma library: [Figma URL with node-id]. Our component lives in src/components/ui/button.tsx. Map every variant.
Does it work in Claude Code?
Only with the Figma MCP server connected, because the skill relies on its get_code_connect_suggestions and get_context_for_code_connect tools. With the server set up, you can copy the folder from GitHub into ~/.claude/skills.