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.
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.4---5# Frontend Figma Handoff67Use this skill when a frontend task depends on Figma files, frames, components,8tokens, or design handoff.910Actual 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.11122026-07-13 review note: v3.6.0 confirmed this skill as a local handoff checklist13around official Figma tooling, not a replacement for the Figma connector or a14copy of private Notion examples.1516## Workflow17181. Confirm the exact Figma file, page, frame, node IDs, and target implementation stack.192. Use the official Figma capability to inspect frames, components, styles, variables, and assets.203. Extract or request design tokens before writing code.214. Identify reusable project components and variants.225. Check accessibility concerns such as contrast, text size, hit targets, and hierarchy.236. Produce implementation notes that preserve design intent while using the project stack and components.247. Verify the rendered app against the Figma frame.2526## Rules2728- Do not rely on implicit page context when multiple agents or sessions may be active.29- Use explicit frame/node identifiers when asking the official Figma tooling to inspect or modify Figma.30- Keep Figma tooling separate from general visual-design skills.31- Prefer existing project components over pixel-copying everything.32- Preserve meaningful design intent, not accidental spacing noise.3334## Useful Tasks3536- Create implementation notes for React/Vue components from selected frames.37- Extract color and typography tokens.38- Audit contrast and hierarchy.39- Prepare safe requests for bulk style updates or asset export through official Figma tooling.40- Create implementation notes for developers.4142## References And Utilities4344- `references/figma-mcp-readme.md`: workflow overview.45- `references/figma-mcp-commands.md`: available MCP commands.46- `references/figma-mcp-installation.md`: setup details for Cursor, Claude, and other tools.47- `references/figma-mcp-troubleshooting.md`: failure modes and fixes.48- `scripts/`: upstream setup, launcher, and integration test utilities.
YuukiAS