How do I install the Figma Integration skill?

Run npx skillmds@latest add zereight/figma-integration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Figma Integration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Figma Integration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Figma Integration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Figma Integration?

zereight (@zereight) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Figma Integration by zereight — Agent Skill

Name: Figma Integration
Author: zereight

Figma Integration

Keep Figma and code in sync — map the 3-tier DTCG tokens to Figma Variables (collections + modes), sync in either direction, use the Figma MCP when connected, and verify component parity (variants/states). Use when the user wants to push tokens/components to Figma, pull a design into code, set up token↔Variable sync, or check design-code drift.

zereight 1656f1b 2.1 KB Updated Sep 17, 2026

File contents

Skill: Figma Integration

Bridge design (Figma) and code (this repo) in both directions. The token JSON stays the source of truth; Figma Variables mirror it.

Steps

Read workflows/figma-integration.md (token↔Variable mapping, sync directions, MCP usage, parity).
Map the 3-tier hierarchy → three Figma collections (Primitives → Semantic → Component) with aliasing; dark/brand/density → Figma Modes (tokens/theming.json).
Choose ONE authoritative sync direction (code→Figma publish, or Figma→code extract via Tokens Studio / Variables REST API). The other side is generated — never hand-edit both.
If a Figma MCP server is connected: prefer its tools/skills (load its mandatory prerequisite skill first). Use it to read frames/variables/screenshots into code, build Variables/components from our tokens, or wire Code Connect to components/*.
Check component parity: Figma variants/properties must cover our variants + sizes + the 8 states; flag gaps.

Verification (definition of done)

Every Figma Variable resolves to a token in tokens/*.json (no orphan hex in designs).
One authoritative direction; the generated side has zero hand edits.
Variant sets cover all 8 states; Code Connect points to the right components/* file.
After any token import: python3 scripts/validate_tokens.py passes.

Kit location

This skill is part of ux-ui-agent-skills v2.4.0.

Resolve every relative path in the steps above against:

.agents/ux-ui-agent-skills/

(from repo root: /Users/tao.exe/Documents/skill/.agents/ux-ui-agent-skills)

Load .agents/ux-ui-agent-skills/CLAUDE.md when you need the full agent persona or Request Router.

---name: figma-integrationdescription: Keep Figma and code in sync — map the 3-tier DTCG tokens to Figma Variables (collections + modes), sync in either direction, use the Figma MCP when connected, and verify component parity (variants/states). Use when the user wants to push tokens/components to Figma, pull a design into code, set up token↔Variable sync, or check design-code drift.---# Skill: Figma IntegrationBridge design (Figma) and code (this repo) in both directions. The token JSON stays the source of truth; Figma Variables mirror it.## Steps1. Read `workflows/figma-integration.md` (token↔Variable mapping, sync directions, MCP usage, parity).2. Map the 3-tier hierarchy → three Figma collections (Primitives → Semantic → Component) with aliasing; dark/brand/density → Figma **Modes** (`tokens/theming.json`).3. Choose ONE authoritative sync direction (code→Figma publish, or Figma→code extract via Tokens Studio / Variables REST API). The other side is generated — never hand-edit both.4. **If a Figma MCP server is connected:** prefer its tools/skills (load its mandatory prerequisite skill first). Use it to read frames/variables/screenshots into code, build Variables/components from our tokens, or wire Code Connect to `components/*`.5. Check component parity: Figma variants/properties must cover our variants + sizes + the 8 states; flag gaps.## Verification (definition of done)- Every Figma Variable resolves to a token in `tokens/*.json` (no orphan hex in designs).- One authoritative direction; the generated side has zero hand edits.- Variant sets cover all 8 states; Code Connect points to the right `components/*` file.- After any token import: `python3 scripts/validate_tokens.py` passes.---## Kit locationThis skill is part of **ux-ui-agent-skills v2.4.0**.Resolve every relative path in the steps above against:`.agents/ux-ui-agent-skills/`(from repo root: `/Users/tao.exe/Documents/skill/.agents/ux-ui-agent-skills`)Load `.agents/ux-ui-agent-skills/CLAUDE.md` when you need the full agent persona or Request Router.

Frequently asked questions