How do I install the Figma Prototype Plan skill?

Run npx skillmds@latest add majiayu000/figma-prototype-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Figma Prototype Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Figma Prototype Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Figma Prototype Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Figma Prototype Plan?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Figma Prototype Plan by majiayu000 — Agent Skill

Name: Figma Prototype Plan
Rating: 4.2 (5 reviews)
Author: majiayu000

Figma Prototype Plan

Plan prototype interactions and flows for user testing in Figma. Use when asked to plan a Figma prototype, set up prototype interactions, define what to prototype for a user test, or prepare a Figma prototype for usability testing. Produces a prototype scope, interaction specification, test task scripts, and Figma setup guide.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Figma Prototype Plan Skill

Plans what to prototype in Figma and how — scoping to what the user test needs, defining every interaction, and setting up the test scenarios. Prevents over-building and ensures the prototype answers the research question.

Required Inputs

Research question (what are you trying to learn?)
Feature or flow being prototyped
Prototype fidelity (low wireframe / mid functional / high pixel-perfect)
Testing method (moderated in-person / moderated remote / unmoderated)
Number of test tasks

Output Structure

1. Prototype Scope

In scope: [Flows with real interactions — specific screens listed] Out of scope: [Screens to show as static — not worth building as interactive] Rationale: Prototypes should be the minimum needed to test the hypothesis.

2. Interaction Specification

Interaction N: [Description]

Trigger: Tap/Swipe/Hover/Form submit
Element: [Figma layer name]
Destination: [Figma frame name]
Animation: Instant/Dissolve/Push left/Push right/Slide up
Timing: [ms]
Reset after: Yes/No

3. Prototype Flow Diagram

[Start frame]
  -> Tap "Action"
[Next frame]
  -> Tap "Complete" -> [Success frame]
  -> Tap "Cancel"   -> [Back to start]

4. Test Task Scripts

Task N: [Title]

Scenario (read to participant): "[Realistic scenario giving context without directing the click path]"

Observing:

[What to watch for]

Success when: [Specific trigger]

5. Figma Setup Guide

Starting frame: [Name]
Device preview: [Device]
Prototype settings: background colour, show device, type
Sharing: Can view link, reset process between participants

6. Build vs Fake Table

Element	Build	Fake	Notes
Primary CTA flow	Yes		Core to research
Secondary nav		Yes	Not being tested
Error state	Yes		Testing recovery

Quality Checks

Scope limited to what the research question requires
Every interaction has a named destination frame
Task scripts are scenario-based (not "click on X")
Success criteria defined for each task
Reset process defined for between participants

Example Trigger Phrases

"Plan the Figma prototype for our user test on [feature]"
"What interactions do I need to build for this prototype?"
"Help me set up a Figma prototype for [research question]"
"Write the test task scripts for our [feature] prototype"
"What should I prototype vs leave as static screens?"

---name: figma-prototype-plandescription: Plan prototype interactions and flows for user testing in Figma. Use when asked to plan a Figma prototype, set up prototype interactions, define what to prototype for a user test, or prepare a Figma prototype for usability testing. Produces a prototype scope, interaction specification, test task scripts, and Figma setup guide.--- # Figma Prototype Plan Skill Plans what to prototype in Figma and how — scoping to what the user test needs, defining every interaction, and setting up the test scenarios. Prevents over-building and ensures the prototype answers the research question. ## Required Inputs - **Research question** (what are you trying to learn?) - **Feature or flow being prototyped** - **Prototype fidelity** (low wireframe / mid functional / high pixel-perfect) - **Testing method** (moderated in-person / moderated remote / unmoderated) - **Number of test tasks** ## Output Structure ### 1. Prototype Scope **In scope:** [Flows with real interactions — specific screens listed] **Out of scope:** [Screens to show as static — not worth building as interactive] **Rationale:** Prototypes should be the minimum needed to test the hypothesis. ### 2. Interaction Specification **Interaction N: [Description]** - Trigger: Tap/Swipe/Hover/Form submit - Element: [Figma layer name] - Destination: [Figma frame name] - Animation: Instant/Dissolve/Push left/Push right/Slide up - Timing: [ms] - Reset after: Yes/No ### 3. Prototype Flow Diagram ``` [Start frame] -> Tap "Action" [Next frame] -> Tap "Complete" -> [Success frame] -> Tap "Cancel" -> [Back to start] ``` ### 4. Test Task Scripts **Task N: [Title]** Scenario (read to participant): "[Realistic scenario giving context without directing the click path]" Observing: - [What to watch for] Success when: [Specific trigger] ### 5. Figma Setup Guide - Starting frame: [Name] - Device preview: [Device] - Prototype settings: background colour, show device, type - Sharing: Can view link, reset process between participants ### 6. Build vs Fake Table | Element | Build | Fake | Notes | |---|---|---|---| | Primary CTA flow | Yes | | Core to research | | Secondary nav | | Yes | Not being tested | | Error state | Yes | | Testing recovery | ## Quality Checks - [ ] Scope limited to what the research question requires - [ ] Every interaction has a named destination frame - [ ] Task scripts are scenario-based (not "click on X") - [ ] Success criteria defined for each task - [ ] Reset process defined for between participants ## Example Trigger Phrases - "Plan the Figma prototype for our user test on [feature]" - "What interactions do I need to build for this prototype?" - "Help me set up a Figma prototype for [research question]" - "Write the test task scripts for our [feature] prototype" - "What should I prototype vs leave as static screens?"

Frequently asked questions