Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alinaqi/user-journeys
User experience flows - journey mapping, UX validation, error recovery
Passed 17 of 22 test cases with the skill, and 10 of 22 without it.
and 9 more in the full report
8 fixed9 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a 'Signup to First Value' critical journey, what is the target time-to-complete metric for a user reaching their 'aha moment' from initial signup?
| Checked | Without skill | With skill |
|---|---|---|
| Sets target duration to reach first value to less than 5 minutes. | Missed | Passed |
The instructions your model reads when the skill loads.
For defining and testing real user experiences - not just specs, but actual flows humans take through your application.
Specs test features. Journeys test experiences.
A feature can pass all specs but still deliver a terrible experience. User journeys capture:
_project_specs/
├── journeys/
│ ├── _template.md # Journey template
│ ├── critical/ # Must-work journeys (revenue, core value)
│ │ ├── signup-to-first-value.md
│ │ ├── checkout-purchase.md
│ │ └── login-to-dashboard.md
│ ├── common/ # Frequent user paths
│ │ ├── browse-and-search.md
│ │ ├── update-profile.md
│ │ └── invite-team-member.md
│ └── edge-cases/ # Error recovery, unusual paths
│ ├── payment-failure-retry.md
│ ├── session-timeout-recovery.md
│ └── offline-reconnection.md
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.