ux-flow-designer

Design end-to-end user flows with triggers, goals, and branch logic for MVPs.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill ux-flow-designer-saranskumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-flow-designer
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/ux-flow-designer
Command: npx skills add https://github.com/saranskumar/anti-slop --skill ux-flow-designer-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design end-to-end user journeys and task flows for a product concept or MVP to clarify movements, decisions, and outcomes before UI planning.

Core Features & Use Cases

  • Define triggers, goals, and success conditions to anchor the flow.
  • Map happy paths with branch points for empty, loading, error, denial, retry, and abandonment states.
  • Identify system actions that occur between user steps and surface friction risks for prioritization.

Quick Start

Provide the trigger, goal, and success condition for a feature, and I will draft the primary user flow with branches and edge cases.

Frequently Asked Questions about ux-flow-designer

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

FAQPage Schema
How do I map end-to-end user flows for an MVP with multiple roles?

To map end-to-end user flows, provide the trigger, goal, and success condition for your product concept. The flow will define onboarding paths, branch logic, and edge states across multiple screens and roles.

What is the best way to handle edge cases in user journey mapping?

Edge cases in user journey mapping are handled by defining branch points for empty, loading, error, denial, retry, and abandonment states alongside the primary happy path to ensure comprehensive flow coverage.

How do I identify friction risks and system actions between user steps?

Friction risks and system actions are identified by mapping the primary user flow and explicitly surfacing system actions that occur between user steps, allowing you to prioritize areas of potential friction.

When do I need to design user flows with decision points before UI planning?

You need to design user flows with decision points before UI planning when an MVP spans multiple screens or roles and requires clear movements, decisions, and outcomes to anchor the interface design.

Can I clarify product concept journeys without detailed UI mockups?

Yes, you can clarify product concept journeys by drafting task flows that map triggers, goals, and success conditions with branch logic, entirely independent of detailed UI mockups.