user-journeys

Maps and validates product journeys including error recovery paths with Playwright-based end-to-end tests.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill user-journeys-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-journeys
Source: https://github.com/lciacci/tessera/tree/main/skills/user-journeys
Command: npx skills add https://github.com/lciacci/tessera --skill user-journeys-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams uncover friction that feature specifications and happy-path tests miss by documenting how people actually use products, including confusion, mistakes, interruptions, and recovery needs.

Core Features & Use Cases

  • Journey Mapping: Document user goals, preconditions, step-by-step actions, system responses, success criteria, and potential friction.
  • UX Validation: Evaluate clarity, speed, forgiveness, accessibility, mobile usability, and layout stability across critical flows.
  • Error Recovery Testing: Define and test recovery paths for payment failures, session timeouts, offline states, authentication problems, and other edge cases.
  • Use Case: Map a signup-to-first-value journey, identify onboarding drop-off points, and create Playwright tests that verify users can recover from common signup and payment failures.

Quick Start

Use the user-journeys skill to map the complete signup-to-first-value experience, including success criteria, friction points, error recovery paths, UX metrics, and corresponding end-to-end tests.

Frequently Asked Questions about user-journeys

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

FAQPage Schema
How do I map user journeys to find friction in critical product flows?

Validate UX by evaluating clarity, speed, forgiveness, accessibility, mobile usability, and layout stability across critical flows, ensuring users can successfully navigate signup, onboarding, checkout, and account management journeys.

Can I use Playwright for end-to-end testing of error recovery paths?

Yes, Playwright validates end-to-end user journeys by testing recovery paths for payment failures, session timeouts, offline states, and authentication problems, verifying users can successfully recover from common edge cases.

What do I need to document before mapping end-to-end user experiences?

Documenting end-to-end user experiences requires documented user goals, journey steps, success criteria, error scenarios, recovery paths, and measurable UX metrics to effectively expose friction and validate critical or recurring product journeys.

How do I test onboarding drop-off points and signup failure recovery?

Test onboarding drop-off by mapping the signup-to-first-value journey, identifying friction points, defining recovery paths for failures, and creating Playwright tests that verify users can recover from common signup and payment errors.

Why does my feature specification miss UX friction that journey mapping finds?

Journey mapping uncovers friction by evaluating clarity, speed, forgiveness, accessibility, mobile usability, and layout stability, exposing failure points and recovery needs that happy-path tests and feature specifications overlook.