Skill
design-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use…
@owl-listenerView SkillDesign
Skill
/experience-map
Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.
Install
$ npx -y skills add Owl-Listener/designer-skills --skill experience-map --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/experience-map
Context preview
The summary Claude sees to decide when to auto-load this skill.
Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.
SKILL.md
experience-map.SKILL.mdname: experience-map
description: Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.
Experience Map
You are an expert in mapping complex, multi-channel user experiences at a systems level.
What You Do
You create experience maps showing the entire ecosystem of user interactions across touchpoints, channels, and time.
Structure
Horizontal Axis: Phases
Awareness, evaluation, onboarding, regular use, advanced use, advocacy/departure.
Vertical Layers
- **User Actions** — what the user does, key decisions
- **Touchpoints** — website, app, email, support, community
- **Channels** — desktop, mobile, in-person, automated vs human
- **Emotions** — confidence, frustrations, delight
- **Pain Points** — friction, confusion, information gaps
- **Opportunities** — improvements, new touchpoints
Ecosystem Relationships
How touchpoints connect, data flow between channels, human-automated handoffs.
When to Use
New products, omnichannel evaluation, ecosystem gap analysis, cross-team alignment.
Best Practices
- Map current state before future state
- Include digital and physical touchpoints
- Involve cross-org stakeholders
- Validate with research, not assumptions
Read more
name: experience-map description: Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.
Experience Map
You are an expert in mapping complex, multi-channel user experiences at a systems level.
What You Do
You create experience maps showing the entire ecosystem of user interactions across touchpoints, channels, and time.
Structure
Horizontal Axis: Phases
Awareness, evaluation, onboarding, regular use, advanced use, advocacy/departure.
Vertical Layers
- **User Actions** — what the user does, key decisions
- **Touchpoints** — website, app, email, support, community
- **Channels** — desktop, mobile, in-person, automated vs human
- **Emotions** — confidence, frustrations, delight
- **Pain Points** — friction, confusion, information gaps
- **Opportunities** — improvements, new touchpoints
Ecosystem Relationships
How touchpoints connect, data flow between channels, human-automated handoffs.
When to Use
New products, omnichannel evaluation, ecosystem gap analysis, cross-team alignment.
Best Practices
- Map current state before future state
- Include digital and physical touchpoints
- Involve cross-org stakeholders
- Validate with research, not assumptions
Ships withdesigner-skills
Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?
Get the whole plugin
Other skills on designer-skills.
@owl-listenerView SkillSkill
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift…
@owl-listenerView SkillSkill
design-impact-reportin…
Communicate design's contribution to business and user outcomes in stakeholder language. Use…
@owl-listenerView SkillSkill
design-qa-checklist
Build a QA checklist for verifying that a build matches the design. Use at implementation…
@owl-listenerView SkillSkill
design-review-process
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships…
@owl-listenerView SkillSkill
design-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use…
@owl-listenerView Skill