user-journeys

Documents and tests end-to-end user experience flows with Playwright journey tests.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dudqks0319-cpu/antigravity-skills --skill user-journeys-dudqks0319-cpu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-journeys
Source: https://github.com/dudqks0319-cpu/antigravity-skills/tree/main/user-journeys
Command: npx skills add https://github.com/dudqks0319-cpu/antigravity-skills --skill user-journeys-dudqks0319-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test.

What problem does it solve? Feature-level specs can all pass while the actual user experience remains broken. This Skill helps you define, document, and test real user journeys—complete flows with emotional states, error recovery, and timing constraints—so you validate experiences, not just features. ## Core Features & Use Cases - Journey Documentation Templates: Structured markdown templates for critical, common, and edge-case journeys with success criteria, friction points, and error scenarios per step. - Playwright Journey Testing: Serial E2E test patterns that verify each journey step, measure completion time, and test error recovery (e.g., payment decline, session timeout). - UX Validation Utilities: Automated checks for page load time, CTA visibility, layout shift (CLS), and accessibility focus management. - Use Case: Define a "Signup to First Value" journey with a 5-minute target, then write Playwright tests that verify the CTA is above the fold, signup completes in under 5 seconds, onboarding is skippable, and users recover gracefully from duplicate-email errors. ## Quick Start Ask the AI to document and test the critical signup-to-first-value user journey for my app using the user-journeys skill.

Frequently Asked Questions about user-journeys

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

FAQPage Schema
How do I write end-to-end user journey tests with Playwright?▼

Structure Playwright tests with test.describe.configure({ mode: 'serial' }) so journey steps run in order. Write one test per journey step verifying success criteria like CTA visibility, URL transitions, and completion time limits.

What is the difference between feature specs and user journey testing?▼

Feature specs verify individual functionality in isolation, while journey testing validates complete user flows including navigation, timing, emotional friction points, and error recovery. A feature can pass specs while the overall experience still fails.

How do I test payment decline recovery in checkout flows?▼

Use Stripe test card 4000000000000002 to trigger a decline, verify a friendly error message appears, confirm the user stays on the checkout page, then retry with card 4242424242424242 to verify successful recovery.

How do I measure page load time and layout shift in Playwright?▼

Use page.evaluate with PerformanceNavigationTiming for load duration and a PerformanceObserver on layout-shift entries to compute CLS. Assert load time under 2000ms and CLS below 0.1 for good UX scores.

What should a user journey document include?▼

Include priority, user type, success metric, a user goal statement, preconditions, per-step actions with success criteria and friction points, error scenarios with recovery paths, metrics to track, and a link to the corresponding E2E test.

When should I not rely only on journey testing?▼

Journey tests are slower and cover fewer permutations than unit or component tests, so they should complement rather than replace lower-level testing. Use them for critical revenue and core-value flows, not every edge case.