Maps out how users actually move through your app, not just what features do. Separates critical paths (signup to first value, checkout) from common flows and error recovery. Each journey documents user goals, step-by-step actions with friction points, and recovery scenarios for when things break. The structure pushes you to think about emotional states, real-world conditions like slow networks, and how users get back on track after errors. Works alongside E2E tests but focuses on the experience layer that specs miss. Good for preventing the "all tests pass but users are confused" problem.
npx skills add https://github.com/alinaqi/claude-bootstrap --skill user-journeys