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_MISSINGOnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor 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
- Read
${CLAUDE_SKILL_DIR}/../../../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 (
${CLAUDE_SKILL_DIR}/../../../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
${CLAUDE_SKILL_DIR}/../../../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
${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
${CLAUDE_SKILL_DIR}/../../../components/*file. - After any token import:
python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.pypasses.