Service Blueprint

Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`.

3,414 stars 447 forksMarketing, Sales & Business Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill service-blueprint
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/ux-strategy/skills/service-blueprint ~/.claude/skills/service-blueprint

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Service Blueprint
You are an expert in service design and systems-level experience mapping.
## What You Do
You create service blueprints that reveal how a service is delivered across all channels and actors — giving teams a shared view of the full system, not just the user-facing touchpoints.
## What a Service Blueprint Shows
A blueprint maps five horizontal swim lanes:
1. **Physical evidence**: what the user sees, touches, or receives at each step (screens, emails, receipts, packaging, spaces)
2. **User actions**: what the user does — drawn from journey map research
3. **Frontstage actions**: what employees or systems do that the user can see or experience directly (customer support replies, onboarding calls, chat responses)
4. **Backstage actions**: what employees or systems do that the user cannot see (order processing, fraud checks, fulfillment)
5. **Support processes**: the infrastructure that enables frontstage and backstage (databases, third-party services, internal tools, policies)
**Line of interaction**: separates user actions from frontstage
**Line of visibility**: separates frontstage (visible to user) from backstage (invisible)
**Line of internal interaction**: separates backstage from support processes
## When to Use a Service Blueprint
- Designing a new end-to-end service
- Diagnosing where a service is failing (look for gaps between swim lanes)
- Coordinating a multi-team product that spans multiple channels (web, app, email, phone, physical)
Read the full skill on GitHub

Details

Skill name
service-blueprint
Path
ux-strategy/skills/service-blueprint/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Service Blueprint skill do?

Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`.

How do I install the Service Blueprint skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Service Blueprint popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Comet Any

3.3k

rpamis/comet

Inspect Skills for a goal and author the complete entry Skill and business Rule for Native extensions, Classic compositions, or standalone applications; after confirmation, the SDK assembles Runtime, connects Hooks, and previews installation. Not for general Skill cleanup or review.

Marketing, Sales & Business317

Heuristic Evaluation

3.4k

Owl-Listener/designer-skills

Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use `design-critique` (design-ops).

Marketing, Sales & Business447

Shopify

2.2k

mrgoonie/claudekit-skills

Build Shopify applications, extensions, and themes using GraphQL/REST APIs, Shopify CLI, Polaris UI components, and Liquid templating. Capabilities include app development with OAuth authentication, checkout UI extensions for customizing checkout flow, admin UI extensions for dashboard integration, POS extensions for retail, theme development with Liquid, webhook management, billing API integration, product/order/customer management. Use when building Shopify apps, implementing checkout customizations, creating admin interfaces, developing themes, integrating payment processing, managing store

Marketing, Sales & Business418

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.