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 into code, set up token↔Variable sync, or check design-code drift.
- Category
- Design systems
- Status
- Experimental
- Use when
- sync tokens with Figma
- push components to Figma
- pull a Figma design into code
- set up Figma Variables from our tokens
- check design-code drift
- Works on
- The project's DTCG token files
- A connected Figma file or Figma MCP server (optional)
- Produces
- A token-to-Figma-Variable collection/mode mapping
- A stated authoritative sync direction
- A component parity report (variant/state coverage gaps)
- Requires
- python, figma-mcp
- Works with
- Claude Code, Codex, Cursor, OpenCode, Amp, Gemini CLI, GitHub Copilot, VS Code
- Tags
- figma, figma-to-code, design-tokens, design-system, component-api, multi-brand
- Source
- plugin87/ux-ui-agent-skills by plugin87 · MIT · adapted for this repository
- Related skills
- design-tokens
Instructions from SKILL.md
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
- Read
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 (
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
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
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.pypasses.
Supporting files
3 more files in this skill's folder. Markdown opens as a page, other text files open as source, and anything else downloads as it is.
Next to SKILL.md1
scripts/1
workflows/1
extract-design-md
Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations.