Edit Figma Design
warpdotdev/warp
Creates or revises Figma designs from a written description using the Figma MCP authoring tools, in a new blank file or an existing one.
Plan user flows and screen states for a Figma design before any designing starts.
Install Figma User Flow Planner
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/figma-user-flow-planner .claude/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .claude/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/figma-user-flow-planner .agents/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .agents/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/figma-user-flow-planner .cursor/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .cursor/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/figma-user-flow-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/figma-user-flow-planner .gemini/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .gemini/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/figma-user-flow-planner .github/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .github/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-user-flow-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/figma-user-flow-planner .opencode/skills/figma-user-flow-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "figma-user-flow-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-user-flow-planner into .opencode/skills/figma-user-flow-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-user-flow-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
figma-user-flow-planner- GitHub stars
- 1.4k
- Token cost
- ~786 tokens
- SKILL.md length
- 357 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan user flows and screen states for a Figma design before any designing starts.
- Works in 6 steps: Flow Overview → Screen Map → State Matrix → …
- Asked to plan a user flow
- SKILL.md covers Required Inputs, Output Structure, Quality Checks and Anti-Patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Figma User Flow Planner is an agent skill from mohitagw15856/pm-claude-skills. Plan user flows and screen states for a Figma design before any designing starts. Use when asked to plan a user flow, map out screens for a feature, define screen states, plan a Figma file structure, or work out what needs to be designed before opening Figma. Produces a complete flow map with all screens, states, entry/exit points, and a suggested Figma page structure.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering UX design. It works with Figma. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to plan a user flow
- Map out screens for a feature
- Define screen states
- Plan a Figma file structure
Example prompts
- “/figma-user-flow-planner”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Figma User Flow Planner loads about 786 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 357 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 357 words, ~786 tokens.
Download SKILL.mdSave it as
.claude/skills/figma-user-flow-planner/SKILL.md (or your agent's skills folder).- name
- figma-user-flow-planner
- description
- Plan user flows and screen states for a Figma design before any designing starts. Use when asked to plan a user flow, map out screens for a feature, define screen states, plan a Figma file structure, or work out what needs to be designed before opening Figma. Produces a complete flow map with all screens, states, entry/exit points, and a suggested Figma page structure.
Figma User Flow Planner Skill
Plans what needs to be designed before a pixel is touched — mapping all screens, states, entry points, and edge cases so designers do not discover missing states mid-build.
Required Inputs
- Feature or task being designed
- User type (who performs this flow?)
- Platform (iOS / Android / Web / Multi-platform)
- Starting point (where does the user begin?)
- Known edge cases (optional)
Output Structure
1. Flow Overview
Feature, user, goal, entry points, success exit, failure exits.
2. Screen Map
| # | Screen name | Type | Triggered by | Notes |
|---|---|---|---|---|
| 1 | [Screen] | New/Modal/Drawer/Toast | [What triggers] | [Considerations] |
Screen types to cover: entry, happy path, loading, success, error (network/validation/permission), empty, first-time/onboarding, edge cases.
3. State Matrix
[Screen name]
| State | Trigger | Visual change | Action available |
|---|---|---|---|
| Default | Page load | [Description] | [What user can do] |
| Loading | User taps action | Skeleton/spinner | None |
| Error | API failure | Error message | Retry/Go back |
| Empty | No data | Empty state | [CTA] |
4. Decision Points
Decision: [Name]
- If yes: [Screen N]
- If no: [Screen X]
5. Suggested Figma File Structure
Feature name/
- Cover
- Flow Map
- Happy Path
- Error States
- Empty States
- Edge Cases
- Handoff6. What Not to Design Yet
[Explicit out-of-scope items — prevents scope creep]
Quality Checks
- All three state types covered: loading, error, empty
- All decision points mapped with both branches
- Entry points include all realistic user paths
- Out-of-scope section is explicit
- Figma file structure matches screen map
Show full SKILL.md (149 more words)Show less
Anti-Patterns
- Do not plan only the happy path — all error states, empty states, and edge cases must be mapped before designing starts
- Do not produce a flow map that doesn't match the Figma file structure — the page structure must reflect the flow map
- Do not define screens without specifying all required states — a screen without its variants is an incomplete design scope
- Do not start designing before entry and exit points are fully documented — unclear boundaries cause scope creep
- Do not plan user flows without tying each step back to a user goal — every screen must justify its existence
Example Trigger Phrases
- "Plan the user flow for [feature] in Figma"
- "What screens do I need to design for [feature]?"
- "Map out the states for [feature] before we start designing"
- "Help me structure my Figma file for [feature]"
- "What do we need to design before handing this to the developer?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/figma-user-flow-planner of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Figma User Flow Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Figma User Flow Planner this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~786 | Automated safety check: Pass | MIT | |
| Edit Figma Designwarpdotdev/warp | 65k | 1 repos | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| UX Audit WalkthroughAIPexStudio/AIPex | 1.3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| UI UX Designeraiskillstore/marketplace | 433 | 7 repos | ~2.4k | Automated safety check: Pass | None | |
| UX Writingcontent-designer/ux-writing-skill | 224 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
UX Audit Walkthrough
AIPexStudio/AIPex
Walks a Figma prototype or live webpage screen by screen and scores it against four minimalist usability principles.
UI UX Designer
aiskillstore/marketplace
Create interface designs, wireframes, and design systems. An agent skill from aiskillstore/marketplace.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Works with
Categories
Questions about Figma User Flow Planner
What does Figma User Flow Planner do?
Plan user flows and screen states for a Figma design before any designing starts. Figma User Flow Planner is an agent skill from mohitagw15856/pm-claude-skills. Plan user flows and screen states for a Figma design before any designing starts.
When should I use Figma User Flow Planner?
Figma User Flow Planner fits situations like: asked to plan a user flow; map out screens for a feature; define screen states; plan a Figma file structure.
How do I install Figma User Flow Planner in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a claude-code`. Or copy the skill folder (skills/figma-user-flow-planner in mohitagw15856/pm-claude-skills) into .claude/skills/figma-user-flow-planner in your project. Claude Code loads it when a task matches its description.
How do I install Figma User Flow Planner in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a codex`. Or copy the skill folder (skills/figma-user-flow-planner in mohitagw15856/pm-claude-skills) into .agents/skills/figma-user-flow-planner in your project. Codex loads it when a task matches its description.
Can I use Figma User Flow Planner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill figma-user-flow-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/figma-user-flow-planner, .gemini/skills/figma-user-flow-planner, .github/skills/figma-user-flow-planner and .opencode/skills/figma-user-flow-planner in your project.
What does Figma User Flow Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Figma User Flow Planner is instructions for the agent only.
Does Figma User Flow Planner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Figma User Flow Planner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Figma User Flow Planner use?
Figma User Flow Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Figma User Flow Planner use?
About 786 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Figma User Flow Planner?
Skills that share tags, products or a category with Figma User Flow Planner: Edit Figma Design (warpdotdev/warp, 65k stars), UX Audit Walkthrough (AIPexStudio/AIPex, 1.3k stars), UI UX Designer (aiskillstore/marketplace, 433 stars) and UX Writing (content-designer/ux-writing-skill, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Figma User Flow Planner?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.