git:20260824.db721b3 to git:20261006.5751441

13 added, 7 removed. Audit A to A.

---

name: figma-integration

description: 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.

- invocation: model

---

# Skill: Figma Integration

+ > **Step 0 — is the kit here?** This skill reads files from the kit. Check once:

+ > `ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING`

+ > On `KIT_MISSING` only the skill folders were installed, which is what

+ > `npx skills add` does. Say so plainly, point the user at

+ > `npx ux-ui-agent-skills init` or the plugin install, and stop. Do not guess the

+ > contents of a file you could not open.

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`).

+ 1. Read `${CLAUDE_SKILL_DIR}/../../../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** (`${CLAUDE_SKILL_DIR}/../../../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/*`.

+ 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 `${CLAUDE_SKILL_DIR}/../../../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).

+ - Every Figma Variable resolves to a token in `${CLAUDE_SKILL_DIR}/../../../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.

+ - Variant sets cover all 8 states; Code Connect points to the right `${CLAUDE_SKILL_DIR}/../../../components/*` file.

+ - After any token import: `python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py` passes.