prototype-to-figma-skill

Convert code prototypes into annotated Figma frames with design system component mapping.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/design-skills --skill prototype-to-figma-skill-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype-to-figma-skill
Source: https://github.com/reason-machines/design-skills/tree/main/skills/prototype-to-figma-skill
Command: npx skills add https://github.com/reason-machines/design-skills --skill prototype-to-figma-skill-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a working code prototype into a reviewable design artifact normally requires manually recreating every screen in Figma, which is slow and error-prone. This Skill automates that handoff by exploding prototype interaction flows into state-by-state Figma frames with annotations, so designers and stakeholders can review and comment without touching code. ## Core Features & Use Cases - State-by-state frame generation: Analyzes prototype source to inventory components and interaction flows, then creates one Figma frame per UI state with flow arrows between them. - Design system mapping: Searches linked Figma libraries for matching components and uses real DS instances; unmatched elements are built from primitives and flagged with "No DS match" badges. - Native Dev Mode annotations: Adds filterable annotations (Interaction, Navigation, Validation, Error Handling, Data Flow, Edge Cases) plus an overview frame with legend, table of contents, and open questions. - Code Connect integration: Optionally creates bidirectional mappings between Figma components and codebase files. - Use Case: After building a login flow prototype in Claude Code, ask the agent to put it in Figma — it creates a new file, generates frames for empty/validation-error/loading/success states, annotates triggers and transitions, and returns a shareable URL for design review. ## Quick Start Ask your AI assistant to convert this prototype into Figma frames with interaction annotations so the design team can review it.

Frequently Asked Questions about prototype-to-figma-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a code prototype into Figma frames?▼

Provide the prototype source and optionally a Figma file URL. The skill analyzes components and interaction flows, creates one frame per UI state, adds flow arrows and Dev Mode annotations, and returns the Figma file URL for review.

What MCP tools are required for Figma prototype conversion?▼

The skill requires the Figma MCP server with tools including use_figma, search_design_system, get_metadata, get_screenshot, create_new_file, and whoami. Code Connect features additionally need get_code_connect_map and send_code_connect_mappings.

What happens when a prototype component has no design system match?▼

The component is built from Figma primitives such as frames and text nodes rather than being skipped. It is flagged with a visible "No DS match" badge so reviewers know it is not an official design system component.

Does this work without providing a Figma file URL?▼

Yes. If no URL is provided, the skill calls whoami to get user info and create_new_file to generate a new Figma file named after the prototype, then builds all frames inside it.

Why are my Figma annotations not visible?▼

Annotations only appear in Figma's Dev Mode, and each annotation must include a category such as Interaction, Validation, or Error Handling. Switch to Dev Mode in Figma to view them.

How are hover and focus micro-interactions handled in Figma output?▼

Micro-interactions like hover, focus, and blur are grouped into a single frame with annotations describing each state, instead of creating separate frames for every minor interaction.