Translates Figma designs into production-ready application code with 1:1 visual fidelity. It ensures consistent integration with the Figma MCP server, proper use of design tokens, and 1:1 visual parity with designs.
Skill Boundaries
- Use this skill when the deliverable is code in the user's repository.
- If the user asks to create/edit/delete nodes inside Figma itself, switch to figma-use.
- If the user asks to build or update a full-page screen in Figma from code or a description, switch to figma-generate-design.
- If the user asks only for Code Connect mappings, switch to figma-code-connect.
- If the user asks to author reusable agent rules (CLAUDE.md/AGENTS.md), switch to figma-create-design-system-rules.
Prerequisites
- Figma MCP server must be connected and accessible
- User must provide a Figma URL in the format: https://figma.com/design/:fileKey/:fileName?node-id=1-2
- :fileKey is the file key
- 1-2 is the node ID (the specific component or frame to implement)
- OR when using figma-desktop MCP: User can select a node directly in the Figma desktop app (no URL required)
- Project should have an established design system or component library (preferred)
Required Workflow
Follow these steps in order.
- Get Node ID
- Fetch Design Context
- Capture Visual Reference
- Download Required Assets
- Translate to Project Conventions
- Achieve 1:1 Visual Parity
- Validate Against Figma
Implementation Rules
Component Organization
- Place UI components in the project's designated design system directory
- Follow the project's component naming conventions
- Avoid inline styles unless truly necessary for dynamic values
Design System Integration
- ALWAYS use components from the project's design system when possible
- Map Figma design tokens to project design tokens
- When a matching component exists, extend it rather than creating a new one
- Document any new components added to the design system
Code Quality
- Avoid hardcoded values - extract to constants or design tokens
- Keep components composable and reusable
- Add TypeScript types for component props
- Include JSDoc comments for exported components
Examples
- Example workflows illustrate translating a Button component from Figma to a reusable project component.
- Example workflows illustrate building a Dashboard layout from a Figma design with responsive behavior.
Best Practices
- Always Start with Context
- Incremental Validation
- Document Deviations
- Reuse Over Recreation
- Design System First
Additional Resources
- Figma MCP Server Documentation
- Figma MCP Server Tools and Prompts
- Figma Variables and Design Tokens