Focus Code Skill Marketplace

Skill Introduction

Overview

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.

Core value

Turns reusable Other know-how into an installable skill, helping users complete github, community, agent-skill-repository, agent-skills work faster.

Target users

Developers, testers, and maintainers who handle Other tasks in Focus Code.
Teams that already trust workflows or content from phuryn.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, agent-skill-repository, agent-skills that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Other, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, agent-skill-repository, agent-skills, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install customer-journey-map-a17274

View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: customer-journey-map description: "Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey."

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions

Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

Map the journey stages (adapt to the product):

Stage	Description
Awareness	How do they first learn about the product?
Consideration	What do they evaluate? What alternatives do they compare?
Acquisition	How do they sign up or purchase?
Onboarding	First experience with the product — time to value
Engagement	Regular usage — building habits
Retention	What keeps them coming back? What might cause churn?
Advocacy	When and why do they recommend the product to others?

For each stage, document:
- Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
- User actions: What they do at this stage
- Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
- Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
- Pain points: Friction, confusion, drop-off risks
- Opportunities: How to improve the experience at this point
Identify critical moments:
- Aha moment: When the user first experiences core value
- Moments of truth: Decision points where they commit or abandon
- Churn triggers: Where users most commonly drop off
Create the journey map table:

Stage Touchpoint User Action Emotion Pain Point Opportunity
Recommend prioritized improvements:
- Which pain points have the highest impact on conversion or retention?
- What quick wins can improve the experience immediately?
- What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.

customer journey map