User Flow Design

What this skill is for

User flow design defines the sequence of states a user moves through to accomplish a goal — from entry point through decision points, branches, error paths, and exit states. A flow is task-level: each step corresponds to a state (a screen, a view, a mode, a prompt, a command invocation), not to a single action within that state.

Load this skill when:

• Users must move through more than one view, command, or mode to accomplish a goal
• The design problem involves multi-step tasks (checkout, onboarding, CLI pipeline, TUI navigation between views)
• Entry points are not obvious or vary (user arrives mid-flow, user resumes an abandoned flow)
• There are decision branches (existing account vs. new account; --dry-run before execution)
• You are designing a CLI pipeline and the failure of any command mid-sequence is a design decision
• TUI navigation between panes, panels, or modes needs to be specified before the interaction within each view

Do NOT load this skill when:

• The problem is limited to what happens within a single view when the user performs an action — that is interaction-design
• The problem is purely about organizing content into categories and navigation paths — that is information-architecture
• The problem is a high-level experience story covering days, channels, or emotional arcs — that is experience-design
• The problem is limited to key binding design or visual layout within a single TUI pane — load tui-design directly