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
Install
npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/figma-integration
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install plugin87-ux-ui-agent-skills@llmmart
git clone https://github.com/plugin87/ux-ui-agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole plugin87/ux-ui-agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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_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.
Files (ux-ui-agent-skills)
-
SKILL.md 2.3 KB
--- 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. --- # 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 `${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 `${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 `${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.py` passes.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.