---
name: Figma Integration
slug: figma-integration
category: Frontend
description: Figma Integration keeps Figma Variables and code tokens in sync in one chosen direction. It is used to publish tokens or components to Figma, extract design data back to code, and verify component parity and design-code drift.
github: "https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/figma-integration"
language: JavaScript
stars: 639
forks: 64
install: "npx degit https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/figma-integration ~/.claude/skills/figma-integration"
installs_to: ~/.claude/skills/figma-integration
source_path: .claude/skills/figma-integration/SKILL.md
collection_size: 17
category_size: 567
collection_url: "https://dirskills.com/collections/plugin87/ux-ui-agent-skills"
added: 2026-08-24T05:18:09.359Z
last_synced: 2026-08-24T05:18:09.359Z
canonical_url: "https://dirskills.com/skills/figma-integration"
---

# Figma Integration

Figma Integration keeps Figma Variables and code tokens in sync in one chosen direction. It is used to publish tokens or components to Figma, extract design data back to code, and verify component parity and design-code drift.

**Install:**

```bash
npx degit https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/figma-integration ~/.claude/skills/figma-integration
```

## README

# 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
1. 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.