Figma prototype

Skill sunhome243/figma-mcp-express/skills/figma-prototype

Use when wiring or auditing Figma prototypes, including clicks, navigation, overlays, transitions, flow starts, scroll-fixed chrome, reaction maps, or inferred flows from static frames. Companion domain skill for figma-mcp-express prototype work.From its SKILL.md

Install

npx -y skills add sunhome243/figma-mcp-express --skill figma-prototype

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, as published. Nobody here has run it

Figma Prototype Wiring

Companion domain layer for prototype judgment. It does not redefine MCP execution rules: use figma-mcp-express for tool discovery, batch syntax, origin/channel, and validation; use this skill for interaction intent, transition choice, overlay limits, flow audits, and scroll-fixed behavior.

First Checks

Figma Desktop open with the plugin running; load the figma-mcp-express skill first for tool/batch discipline.
Prototype reactions live on ANY node (buttons, instances), not just frames — and prototypes are per-page.
Overlay appearance (position/scrim/dismiss) is read-only via the API. You can open an overlay (navigation:"OVERLAY") but not place or style it — that is configured in the Figma UI on the destination frame.

Workflow

Scope — given nodeIds, wire those frames; otherwise use the current page.
Read current state — run get_prototype for starts, edges, overlays, and existing reactions.
Analyze frames — use get_design_context for structure and scan_text_nodes for CTA labels.
Infer only with evidence — require at least two corroborating signals before auto-wiring; flag single-signal guesses.
Wire — batch set_reactions ops plus set_prototype_start for the entry frame.
Choose transitions by similarity — near-identical screens use SMART_ANIMATE; distinct screens use directional PUSH; peers use DISSOLVE; overlays use MOVE_IN/MOVE_OUT.
Verify — re-run get_prototype; flag dead ends, missing back paths, mobile hover triggers, unwired CTAs, and heavy PUSH between same-named frames.

Reference Router

Need	Read
Actions, triggers, transitions, overlays, component variants, flow starts	`references/prototype-patterns.md`
Infer flow from static frames, audit existing prototypes, reaction maps, conservative fixes	`references/prototype-audit.md`
Scrollable frames, sticky headers, pinned tab bars, fixed children	`references/prototype-scroll.md`

Cannot Do

Set overlay position/scrim/dismiss (read-only API) — only open the overlay.
State interactions belong on the component variants (CHANGE_TO), not stamped per instance from outside.
Create files, FigJam, or Slides.