skills/dami-randle/journey-map/SKILL.md
Create customer journey maps for user flows and workflows. Use when the user asks to "map the journey", "analyze user flow", "document the workflow", "trace the path", or needs to understand end-to-end user experiences.
npx skillsauth add aiskillstore/marketplace journey-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Map customer journeys to understand end-to-end user experiences, identify pain points, and discover opportunities for improvement.
Typical phases to map:
| Phase | Description | |-------|-------------| | Awareness | User realizes they need something | | Consideration | User evaluates options | | Decision | User commits to action | | Action | User completes the task | | Retention | User returns or continues |
For each step, document:
Map emotional state through the journey:
Delighted ●───────────●
Satisfied ●───●
Neutral ●───●
Frustrated ●───●
Abandoned ●
## Customer Journey Map: [Journey Name]
### Context
- **Persona**: [User type]
- **Goal**: [What they want to achieve]
- **Trigger**: [What started this journey]
### Journey Overview
| Phase | Step | Action | Emotion | Pain Point |
|-------|------|--------|---------|------------|
| Awareness | 1 | ... | ... | ... |
### Detailed Steps
#### Step 1: [Name]
- **User Action**: What they do
- **System Response**: What happens
- **User Thought**: "What they're thinking"
- **Emotion**: [emoji + description]
- **Pain Points**: Issues encountered
- **Opportunities**: Ways to improve
### Emotion Curve
[Visual representation]
### Key Insights
1. [Critical finding]
2. [Opportunity identified]
### Recommendations
| Priority | Improvement | Impact |
|----------|-------------|--------|
| P0 | ... | High |
Works best with:
ux-expert agent for journey analysisux-audit skill for touchpoint evaluationdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.