Map user journeys and output a user-flows.md with screens to build.
npx skills add https://github.com/gvkhosla/founder-skills --skill ux-flow-designer
Please help me install this Agent Skill. Skill: ux-flow-designer Source: https://github.com/gvkhosla/founder-skills/tree/main/skills/design/ux-flow-designer Command: npx skills add https://github.com/gvkhosla/founder-skills --skill ux-flow-designer
Maps your product's user journeys and identifies the key screens to build. Use when you're about to start building but haven't mapped how users will actually move through the product, or when flows feel unclear. Produces a user-flows.md with step-by-step journeys for your 2–3 most important user paths.
Describe your product and the 2–3 critical user actions, then run ux-flow-designer to produce user-flows.md.
High-intent search queries and answers about installing and using this skill.
To map user flows before building, describe your product and the 2–3 critical user actions to generate a user-flows.md. This document details step-by-step journeys, emotions per step, and implied screens, providing a prioritized build order for your team.
Emotional journey mapping in UX design tracks user feelings at each step of a critical flow. This Skill documents emotions per step within a user-flows.md file, helping you understand psychological friction before identifying the screens needed for your build order.
You identify which screens to build first by mapping your 2–3 critical user flows to produce a structured document. This outputs a user-flows.md detailing those flows and a prioritized list of implied screens, clarifying the build order when paths feel unclear.
Yes, you can use a markdown document to prioritize UI screen build order. This Skill generates a user-flows.md file that structures step-by-step journeys, emotions, and a specific list of screens to build, enabling clear development prioritization.
The best way to document critical user paths is generating a user-flows.md file containing step-by-step journeys and emotions per step. This structured markdown artifact provides your development team with a clear, build-ready list of screens to prioritize.
adidactaMap an MVP aha moment into features and high-level requirements.
sizukutamagoGenerate screen inventories and Mermaid transition diagrams from user stories in docs/requirements.
686f6c61Analyze user flows to identify friction points and propose simplifications.
micserrGenerate user journey maps and flow diagrams in Mermaid and Markdown.
