user-flows-and-guided-paths

Installation
SKILL.md

User Flows and Guided Paths

Related features that belong together should be experienced as a single coherent journey — not as separate screens the user has to navigate between manually. A well-designed flow feels inevitable: each step leads naturally to the next, the user always knows where they are and what comes next, and the path fits the product's information hierarchy.

When to Guide vs. When to Let Users Explore

Scenario Pattern
Linear process with a clear end goal (checkout, signup, setup) Guided step-by-step flow or wizard
Complex task that benefits from breaking into stages Wizard with progress indicator
Feature discovery across an existing product Contextual tooltips or coach marks
User returning to complete something they started Resume prompt with clear re-entry point
Open-ended exploration (dashboard, settings) Free navigation — do not force a flow

Only guide when the task genuinely has a natural order. Forcing a wizard onto a non-sequential task frustrates users who already know what they want.

A discovery cue is a bounded reminder. A badge, glow or nudge pointing at a hidden feature shows only while there is something unseen, ends on first open, and stops after a fixed cap of showings set once for the product. Start with about three and change it only on evidence. Left on for as long as the content exists, it becomes noise the user learns to ignore.

The Wizard Pattern

Installs
1.1K
GitHub Stars
195
First Seen
Apr 19, 2026