Skip to content
Back to search

journey-mapper

Service design journey mapping skills for Claude Code

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/joeyvansommeren--journey-mapper/badge.svg)](/listings/joeyvansommeren--journey-mapper)

HTML

<a href="/listings/joeyvansommeren--journey-mapper"><img src="/api/listings/joeyvansommeren--journey-mapper/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code — via plugin marketplace

/plugin marketplace add joeyvansommeren/journey-mapper
/plugin install journey-mapper@journey-mapper

Update later with `/plugin marketplace update`.

Plugin skills are namespaced by plugin name, so a plugin install is invoked as `/journey-mapper:journey-mapper`. Claude also picks it up automatically when you ask for a journey map.

Claude Code — manual

git clone https://github.com/joeyvansommeren/journey-mapper
cp -r journey-mapper/skills/journey-mapper ~/.claude/skills/journey-mapper

A manual install is invoked as plain `/journey-mapper`. For a single project, copy it to `.claude/skills/journey-mapper` in that repo instead.

---

Other agents — Codex, Cursor, OpenCode, Gemini CLI, GitHub Copilot, Windsurf

These tools all read [Agent Skills](https://agentskills.io) folders natively, and all of them look in the shared `.agents/skills` location. One copy covers every one of them:

git clone https://github.com/joeyvansommeren/journey-mapper
mkdir -p ~/.agents/skills
cp -r journey-mapper/skills/journey-mapper ~/.agents/skills/journey-mapper

For a single project, copy it to `.agents/skills/journey-mapper` in that repo instead. Keep `REFERENCE.md` and `TEMPLATE.html` next to `SKILL.md` — the skill refers to them by relative path.

| Tool | How to invoke | |---|---| | Codex CLI | `$journey-mapper`, or pick it from `/skills` | | Cursor | `/journey-mapper` in Agent chat | | OpenCode | Ask for a journey map — it loads the skill automatically | | Gemini CLI | Ask for a journey map and confirm activation; check with `/skills list` | | GitHub Copilot (CLI and VS Code agent mode) | Mention `/journey-mapper` in your prompt; run `/skills reload` after installing | | Windsurf / Devin Desktop (Cascade) | `@journey-mapper` |

Every tool also triggers the skill on its own when you ask for a journey map or service blueprint.

---

Continue.dev

Continue reads skill folders from its own directory rather than `.agents/skills`:

mkdir -p ~/.continue/skills
cp -r journey-mapper/skills/journey-mapper ~/.continue/skills/journey-mapper

For a single project, use `.continue/skills/journey-mapper`.

---

Aider

Aider has no skill support. Load the skill files read-only instead:

aider --read path/to/journey-mapper/skills/journey-mapper/SKILL.md \
      --read path/to/journey-mapper/skills/journey-mapper/REFERENCE.md

Then ask for a journey map, and point Aider at `TEMPLATE.html` in the same folder.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "journey-mapper",
  3. "description": "Service design journey mapping skills for Claude Code",
  4. "owner": {
  5. "name": "Joey van Sommeren",
  6. "url": "https://github.com/joeyvansommeren"
  7. },
  8. "plugins": [
  9. {
  10. "name": "journey-mapper",
  11. "description": "Scans a codebase and generates a self-contained HTML service-design journey map using the NN/g combined customer journey + service blueprint format.",
  12. "source": "./skills/journey-mapper",
  13. "version": "1.2.0"
  14. }
  15. ]
  16. }
README.md · README · 181 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Journey Mapper
  2. A Claude Code skill that scans any codebase and generates a self-contained HTML service-design journey map — no manual diagram work required.
  3. The output is an NN/g combined **customer journey map + service blueprint** in a single browser-ready HTML file. Open it, annotate it, share it. No server, no build step, no dependencies beyond a browser.
  4. ---
  5. ## What it does
  6. Point it at a codebase. The skill reads your routes, components, API calls, email templates, and error states, then thinks like a service designer: who are the actors, what are their goals, what do they do and feel at each moment?
  7. Every inferred value is flagged `[Assumption]` so you know what needs validating with real users. The Frontstage, Backstage, and Support rows are sourced directly from the code — named components, real API calls, actual services.
  8. ---
  9. ## Install
  10. ### Claude Code — via plugin marketplace
  11. ```
  12. /plugin marketplace add joeyvansommeren/journey-mapper
  13. /plugin install journey-mapper@journey-mapper
  14. ```
  15. Update later with `/plugin marketplace update`.
  16. Plugin skills are namespaced by plugin name, so a plugin install is invoked as `/journey-mapper:journey-mapper`. Claude also picks it up automatically when you ask for a journey map.
  17. ### Claude Code — manual
  18. ```bash
  19. git clone https://github.com/joeyvansommeren/journey-mapper
  20. cp -r journey-mapper/skills/journey-mapper ~/.claude/skills/journey-mapper
  21. ```
  22. A manual install is invoked as plain `/journey-mapper`. For a single project, copy it to `.claude/skills/journey-mapper` in that repo instead.
  23. ---
  24. ### Other agents — Codex, Cursor, OpenCode, Gemini CLI, GitHub Copilot, Windsurf
  25. These tools all read [Agent Skills](https://agentskills.io) folders natively, and all of them look in the shared `.agents/skills` location. One copy covers every one of them:
  26. ```bash
  27. git clone https://github.com/joeyvansommeren/journey-mapper
  28. mkdir -p ~/.agents/skills
  29. cp -r journey-mapper/skills/journey-mapper ~/.agents/skills/journey-mapper
  30. ```
  31. For a single project, copy it to `.agents/skills/journey-mapper` in that repo instead. Keep `REFERENCE.md` and `TEMPLATE.html` next to `SKILL.md` — the skill refers to them by relative path.
  32. | Tool | How to invoke |
  33. |---|---|
  34. | Codex CLI | `$journey-mapper`, or pick it from `/skills` |
  35. | Cursor | `/journey-mapper` in Agent chat |
  36. | OpenCode | Ask for a journey map — it loads the skill automatically |
  37. | Gemini CLI | Ask for a journey map and confirm activation; check with `/skills list` |
  38. | GitHub Copilot (CLI and VS Code agent mode) | Mention `/journey-mapper` in your prompt; run `/skills reload` after installing |
  39. | Windsurf / Devin Desktop (Cascade) | `@journey-mapper` |
  40. Every tool also triggers the skill on its own when you ask for a journey map or service blueprint.
  41. ---
  42. ### Continue.dev
  43. Continue reads skill folders from its own directory rather than `.agents/skills`:
  44. ```bash
  45. mkdir -p ~/.continue/skills
  46. cp -r journey-mapper/skills/journey-mapper ~/.continue/skills/journey-mapper
  47. ```
  48. For a single project, use `.continue/skills/journey-mapper`.
  49. ---
  50. ### Aider
  51. Aider has no skill support. Load the skill files read-only instead:
  52. ```bash
  53. aider --read path/to/journey-mapper/skills/journey-mapper/SKILL.md \
  54. --read path/to/journey-mapper/skills/journey-mapper/REFERENCE.md
  55. ```
  56. Then ask for a journey map, and point Aider at `TEMPLATE.html` in the same folder.
  57. ---
  58. ## Usage
  59. Open a session with a codebase in scope and run:
  60. ```
  61. /journey-mapper
  62. ```
  63. (Installed via the Claude Code plugin marketplace? Use `/journey-mapper:journey-mapper`.)
  64. If the codebase path isn't clear from context, the skill asks. You can also be explicit:
  65. ```
  66. /journey-mapper Scan src/ and save the output to docs/journey-map.html
  67. ```
  68. ---
  69. ## Output
  70. A single `.html` file you can open in any browser:
  71. - **Left rail** — all journeys grouped by category, sticky navigation
  72. - **Journey grid** — NN/g combined customer journey + service blueprint per journey
  73. - **Emotion curve** — renders automatically once feelings are set on two or more moments
  74. - **Export / Import** — JSON-based annotation sharing for team collaboration
  75. - **localStorage autosave** — all edits persist between browser sessions
  76. - **Help modal** — press `?` for a usage guide
  77. **AI fills in (read-only):** Doing · Frontstage · Backstage · Support processes
  78. **You fill in (editable):** Thinking · Feeling · Pain points · Opportunities · Evidence · Notes
  79. ---
  80. ## Customising the template
  81. The visual design lives in `skills/journey-mapper/TEMPLATE.html`. Edit the CSS variables in `:root` to match your brand. The AI only ever replaces the JSON data block, so your styling changes are safe.
  82. `build.py` fills the template by finding three markers: `<title>Journey Maps</title>`, `<h1>Journey Maps</h1>`, and the `<script type="application/json" id="journeys-data">` block. Keep those as they are; the script refuses to build if one is missing.
  83. Default palette: warm stone neutrals, amber accent (`#fcd34d`), Inter typeface.
  84. ---
  85. ## Staying up to date
  86. ```bash
  87. cd ~/wherever-you-cloned-it
  88. git pull
  89. cp -r skills/journey-mapper ~/.agents/skills/journey-mapper # or ~/.claude/skills for Claude Code
  90. ```
  91. Via the Claude Code plugin marketplace: `/plugin marketplace update`.
  92. ---
  93. ## Suggesting improvements
  94. Issues are welcome — if something doesn't work, a journey type isn't covered, or you have an idea for the template, open one. I review suggestions and implement what fits.
  95. PRs: open an issue first. I keep the keys to `main` for now, but good ideas will make it in.
  96. ---
  97. ## Development
  98. The skill ships a small build script, `skills/journey-mapper/build.py` (Python 3.8+, standard library only). The AI writes its journey data to a JSON file and runs the script, which checks the data and fills in the template. Errors come back as a list instead of a broken page.
  99. | Command | What it does | Cost |
  100. |---|---|---|
  101. | `make check` | Unit tests for `build.py`, plus `claude plugin validate --strict` | Free |
  102. | `make eval-quick` | One run of each [plugin eval](https://code.claude.com/docs/en/plugin-evals) case | Real model calls, capped at $5 |
  103. | `make eval` | Three runs per case, with and without the skill for comparison | Real model calls, capped at $15 |
  104. The eval cases live in `evals/`. `maps-sample-app` generates a small Next.js invoicing app and checks that the skill writes a real map from it; `ignores-unrelated-request` checks the skill stays out of unrelated work.
  105. ---
  106. ## Skill index
  107. | Skill | Invocation | What it does |
  108. |---|---|---|
  109. | journey-mapper | `/journey-mapper` | Scans a codebase and generates a complete HTML journey map |
  110. ---
  111. ## License
  112. Apache-2.0 — see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.