Frontend Figma Handoff
Use this skill when a frontend task depends on Figma files, frames, components,
tokens, or design handoff.
Actual Figma file inspection, node edits, asset export, Code Connect, or design generation should use the official Figma capability and its required skill flow. This repository skill only defines the handoff checklist and implementation boundary.
2026-07-13 review note: v3.6.0 confirmed this skill as a local handoff checklist
around official Figma tooling, not a replacement for the Figma connector or a
copy of private Notion examples.
Workflow
- Confirm the exact Figma file, page, frame, node IDs, and target implementation stack.
- Use the official Figma capability to inspect frames, components, styles, variables, and assets.
- Extract or request design tokens before writing code.
- Identify reusable project components and variants.
- Check accessibility concerns such as contrast, text size, hit targets, and hierarchy.
- Produce implementation notes that preserve design intent while using the project stack and components.
- Verify the rendered app against the Figma frame.
Rules
- Do not rely on implicit page context when multiple agents or sessions may be active.
- Use explicit frame/node identifiers when asking the official Figma tooling to inspect or modify Figma.
- Keep Figma tooling separate from general visual-design skills.
- Prefer existing project components over pixel-copying everything.
- Preserve meaningful design intent, not accidental spacing noise.
- Treat Figma as authority only when the project or user names it as canonical;
no-Figma work remains a normal Frontend Design path through another durable
authority or current production grammar for narrow fixes.
- For material design changes, close the design-source gap before letting
implementation drift become the new authority.
- For round-trip work, record what changed in Figma, what changed in code, and
how the rendered result converges back to the canonical frame.
Useful Tasks
- Create implementation notes for React/Vue components from selected frames.
- Extract color and typography tokens.
- Audit contrast and hierarchy.
- Prepare safe requests for bulk style updates or asset export through official Figma tooling.
- Create implementation notes for developers.
References And Utilities
references/figma-mcp-readme.md: workflow overview.
references/figma-mcp-commands.md: available MCP commands.
references/figma-mcp-installation.md: setup details for Cursor, Claude, and other tools.
references/figma-mcp-troubleshooting.md: failure modes and fixes.
scripts/: upstream setup, launcher, and integration test utilities.
1---2name: figma-design-to-code3description: "Plan Figma-to-code handoff: identify frames, tokens, assets, accessibility risks, and implementation notes that complement official Figma tooling."4status: active5provenance: local6trusted: false7requires_network: false8writes_files: true9executes_code: false10secrets_needed:11last_reviewed: 2026-07-1312profile_tags:13recommended_scope: project14icon_small: assets/app-facing.svg15icon_large: assets/app-facing.svg16metadata:17 source: https://skillmd.com/skills/yuukias/figma-design-to-code18---1920# Frontend Figma Handoff2122Use this skill when a frontend task depends on Figma files, frames, components,23tokens, or design handoff.2425Actual Figma file inspection, node edits, asset export, Code Connect, or design generation should use the official Figma capability and its required skill flow. This repository skill only defines the handoff checklist and implementation boundary.26272026-07-13 review note: v3.6.0 confirmed this skill as a local handoff checklist28around official Figma tooling, not a replacement for the Figma connector or a29copy of private Notion examples.3031## Workflow32331. Confirm the exact Figma file, page, frame, node IDs, and target implementation stack.342. Use the official Figma capability to inspect frames, components, styles, variables, and assets.353. Extract or request design tokens before writing code.364. Identify reusable project components and variants.375. Check accessibility concerns such as contrast, text size, hit targets, and hierarchy.386. Produce implementation notes that preserve design intent while using the project stack and components.397. Verify the rendered app against the Figma frame.4041## Rules4243- Do not rely on implicit page context when multiple agents or sessions may be active.44- Use explicit frame/node identifiers when asking the official Figma tooling to inspect or modify Figma.45- Keep Figma tooling separate from general visual-design skills.46- Prefer existing project components over pixel-copying everything.47- Preserve meaningful design intent, not accidental spacing noise.48- Treat Figma as authority only when the project or user names it as canonical;49 no-Figma work remains a normal Frontend Design path through another durable50 authority or current production grammar for narrow fixes.51- For material design changes, close the design-source gap before letting52 implementation drift become the new authority.53- For round-trip work, record what changed in Figma, what changed in code, and54 how the rendered result converges back to the canonical frame.5556## Useful Tasks5758- Create implementation notes for React/Vue components from selected frames.59- Extract color and typography tokens.60- Audit contrast and hierarchy.61- Prepare safe requests for bulk style updates or asset export through official Figma tooling.62- Create implementation notes for developers.6364## References And Utilities6566- `references/figma-mcp-readme.md`: workflow overview.67- `references/figma-mcp-commands.md`: available MCP commands.68- `references/figma-mcp-installation.md`: setup details for Cursor, Claude, and other tools.69- `references/figma-mcp-troubleshooting.md`: failure modes and fixes.70- `scripts/`: upstream setup, launcher, and integration test utilities.