What problem does it solve? Design work often defaults to sterile data, frameworks, and optimization, leaving journeys, blueprints, briefs, and decks structurally complete but emotionally lifeless. This Skill gives design artifacts narrative structure so stakeholders can understand and care about the user's experience without sacrificing evidentiary rigor. ## Core Features & Use Cases - Four canonical narrative patterns: protagonist-arc for empathy, choreography for service coordination, situation/complication/resolution for strategic orientation, and what-is/what-could-be for persuasion, each with a defined goal, shape, and named pathology. - Discipline guardrails: five explicit refusals that prevent smoothing user data into clean arcs, manufacturing tension, substituting emotion for evidence, assuming conflict arcs are universal, or engineering stakeholder assent. - Use Case: A designer has a user journey map that is factually accurate but fails to move stakeholders. Invoke this Skill to apply the protagonist-arc pattern, surfacing the emotional curve of the real user data while flagging where evidence is too thin to support an honest arc. ## Quick Start Ask the assistant to tell the story of your user journey or design brief using the storytelling skill, stating whether your goal is empathy, coordination, orientation, or persuasion.
