One-click install
npx skills add https://github.com/snuffomega/pricechart --skill storytelling-snuffomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storytelling
Source: https://github.com/snuffomega/pricechart/tree/main/.agents/skills/storytelling
Command: npx skills add https://github.com/snuffomega/pricechart --skill storytelling-snuffomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Storytelling structures design work into an emotionally legible narrative so stakeholders can understand the user experience and design rationale as a coherent whole without turning story into unsupported “evidence” or manufactured conflict.

Core Features & Use Cases

  • Four canonical narrative patterns mapped to design moves: protagonist-arc (empathy), choreography (coordination), situation → complication → resolution (orientation), and what-is / what-could-be (persuasion/inspiration).
  • Discipline and refusal rules that prevent common failure modes like smoothing messy user data, manufacturing tension to fit a proposal, substituting emotion for proof, assuming a universal conflict arc, or engineering stakeholder assent by shortcut.
  • Best-fit activation for design communication when an artifact feels lifeless or structurally complete but emotionally sterile, especially for journeys, blueprints, briefs, strategy narratives, and stakeholder-facing presentations.

Quick Start

Use the storytelling skill to shape your design artifact by asking: “Tell the story of this user/service/strategy using a protagonist-arc (or the pattern that fits), and flag where the evidence is too thin to fictionalize.”

Frequently Asked Questions about storytelling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure user journey narratives for stakeholder alignment?

User journey narratives for stakeholder alignment are structured by mapping design work to canonical patterns like protagonist-arc or situation-complication-resolution, ensuring emotional truth is conveyed without substituting evidence. This makes user experience and design rationale legible to teams.

What is the best way to communicate design rationale without manufacturing tension?

Communicating design rationale without manufacturing tension requires applying discipline and refusal rules that prevent smoothing messy user data or engineering stakeholder assent. Use narrative patterns to convey emotional truth while flagging where evidence is too thin to fictionalize.

How do I turn a service blueprint into a strategy narrative?

Turning a service blueprint into a strategy narrative involves applying the what-is or what-could-be pattern to orient and persuade stakeholders. This shapes structurally complete but emotionally sterile artifacts into persuasive strategy communication.

When should I use narrative patterns in design communication?

Narrative patterns in design communication should be used when an artifact feels lifeless or emotionally sterile, particularly for journeys, service blueprints, briefs, and stakeholder-facing presentations. They make user experience and rationale legible as a coherent whole.

Why does stakeholder communication fail when using story structure?

Stakeholder communication fails when story structure substitutes emotion for proof, assumes a universal conflict arc, or smooths messy user data. The storytelling skill enforces refusal checks to prevent these failure modes and ensure narratives do not manipulate assent.

Can I use this storytelling approach for design briefs and strategy narratives?

Yes, this storytelling approach applies to design briefs and strategy narratives by using the choreography pattern for coordination or the protagonist-arc for empathy. It structures design work into emotionally legible narratives that convey rationale without unsupported evidence.