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, while explicitly refusing to let storytelling replace evidence. ## 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 named pathology to avoid. - 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 complete but flat user journey. Invoke the skill to apply the protagonist-arc pattern, mapping the user's goal, tension curve, and resolution while flagging where the data is too thin to support an honest arc. ## Quick Start Ask the assistant to use story mode to tell the story of this user journey and identify which narrative pattern fits the goal.
