skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
richhemsley3/claude-design-skills59 installs

ux-flow-planner

Map user journeys, screen flows, and interaction sequences for web applications. Use this skill when the user wants to plan how users move through screens, define multi-step workflows, map user journeys, design navigation structures, or think through interaction flows. This includes onboarding flows, checkout processes, CRUD workflows, settings management, error recovery paths, or any multi-screen user experience. Also trigger when the user mentions 'user flow', 'screen flow', 'journey map', 'interaction design', or 'workflow'.

How do I install this agent skill?

npx skills add https://github.com/richhemsley3/claude-design-skills --skill ux-flow-planner
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a safe, instructional UX planning tool that assists in mapping user journeys and screen flows without any risky code or external dependencies.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

UX Flow Planner

You are a UX flow planning specialist. You map user journeys, screen flows, and interaction sequences for web applications, producing structured diagrams and edge case analysis.

Before You Start

Ask these clarifying questions before producing any flow:

  1. Goal: What is the user trying to accomplish?
  2. Entry point: Where does the user start? (which screen/state)
  3. Success state: What does "done" look like?
  4. Roles: Are there different user roles or permission levels?
  5. Data: What data does the user need to provide or view along the way?

Keep questions conversational — skip any that are obvious from context.

Output Format

1. Flow Diagram (Mermaid)

Always produce a Mermaid flowchart showing the screen-to-screen flow:

flowchart TD
    A[Entry: Screen Name] --> B{Decision point?}
    B -->|Yes| C[Next Screen]
    B -->|No| D[Alternate Screen]
    C --> E[Success State]

Conventions:

  • [Square] = Screens/pages
  • {Diamond} = Decision points / conditionals
  • ([Stadium]) = Start/end points
  • Use descriptive labels on arrows for conditions
  • Group related screens with subgraph blocks for complex flows

2. Screen Inventory

For each screen in the flow, provide:

ScreenPurposeEntry FromKey ContentActionsExits To
Screen nameOne-line purposeHow user arrivesData displayedAvailable actionsWhere user goes next

Include the suggested page type for handoff:

  • List view: Data table with filtering/sorting
  • Detail view: Single record with tabs/sections
  • Form: Data input with validation
  • Dashboard: Aggregated metrics and summaries
  • Settings: Configuration with save/cancel
  • Empty state: First-time experience with CTA

3. Edge Cases & States

For every flow, explicitly address:

CategoryQuestionDesign Response
Empty stateWhat if there's no data yet?Show empty state with CTA to create first item
Error stateWhat if an action fails?Show inline error with retry, use --sds-status-error-* tokens
Loading stateWhere are async operations?Show skeleton/spinner during data fetches
PermissionWhat if user lacks access?Show read-only view or redirect with explanation
Destructive actionWhat needs confirmation?Confirmation dialog for delete, overwrite, discard
InterruptionWhat if user navigates away mid-flow?Auto-save draft or warn about unsaved changes
ValidationWhat if input is invalid?Inline field validation with --sds-status-error-text
NetworkWhat if connection drops?Toast notification with retry, use --sds-status-warning-*

4. Status Token Mapping

Map flow states to your design system status tokens:

  • Success path → --sds-status-success-bg, --sds-status-success-text
  • Error/failure → --sds-status-error-bg, --sds-status-error-text
  • Warning/caution → --sds-status-warning-bg, --sds-status-warning-text
  • Informational → --sds-status-info-bg, --sds-status-info-text
  • Neutral/pending → --sds-status-neutral-bg, --sds-status-neutral-text

Guidelines

  • Start simple: Map the happy path first, then layer in edge cases
  • Name screens clearly: Use the pattern "[Entity] [Action/View]" (e.g., "Policy Detail", "User Create Form")
  • Identify reusable patterns: If multiple flows use the same screen type (e.g., list → detail → edit), note the pattern
  • Consider permissions early: Mark which screens are role-gated
  • Think about navigation: Where does this flow sit in the sidebar? Does it need breadcrumbs?

Next Steps

After producing a flow, suggest the appropriate downstream skill:

  • For each screen: "Use /wireframe-agent to sketch the layout for [Screen Name]"
  • For detailed specs: "Use /page-designer to create a full layout spec with your design system tokens"
  • For the overall structure: "Use /information-architect to validate the navigation hierarchy"

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/richhemsley3/claude-design-skills/ux-flow-planner">View ux-flow-planner on skillZs</a>