Skill: Figma Integration

In this project, the DTCG .claude/skills/_ux-ui-shared/tokens/*.json are upstream; Figma is a downstream sync target (no longer the sole source). Pull from Figma with scripts/figma/figma-pull.mjs; push tokens→Variables to mirror code. For building UI, defer to shadcn-ui-design.

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 .claude/skills/_ux-ui-shared/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/skills/_ux-ui-shared/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 .claude/skills/_ux-ui-shared/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 .claude/skills/_ux-ui-shared/scripts/validate_tokens.py passes.