dragoon0x/everything-design-taste

user-journey-mapping

Journey map creation, touchpoint analysis, and experience mapping techniques.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill user-journey-mapping

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,247 B
  • docs SUMMARY.md 105 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

User Journey Mapping

Journey Map Structure

Columns (Stages)

  • Awareness → Consideration → Decision → Onboarding → Usage → Advocacy
  • Or define custom stages based on your product.

Rows

  • Actions: What the user does at each stage.
  • Touchpoints: Where they interact (website, app, email, support).
  • Thoughts: What they're thinking.
  • Emotions: How they feel (plot as a line: positive to negative).
  • Pain Points: Specific frustrations.
  • Opportunities: Where you can improve.

Creation Process

  1. Define the persona (who is on this journey).
  2. Define the scope (start and end points).
  3. Research (interviews, analytics, support data).
  4. Map the current state.
  5. Identify pain points and opportunities.
  6. Prioritize improvements.

Common Mistakes

  • Mapping the ideal journey instead of the actual journey.
  • Making it too detailed (forest for the trees).
  • Not involving cross-functional stakeholders.
  • Creating it once and never updating.
  • Journey maps without action items.