Use when outlining a story, screenplay, novel, or narrative and need to establish its structural backbone
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill design-story-structure --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Story Structure?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-design-story-structure)More formats (shields.io, HTML) on the badges page.
---
name: design-story-structure
description: Use when outlining a story, screenplay, novel, or narrative and need to establish its structural backbone
source: "Save the Cat! (Blake Snyder, 2005); The Writer's Journey (Christopher Vogler, 1992); Story (Robert McKee, 1997)"
tags: [storytelling, structure, screenplay, novel, three-act, beat-sheet]
verified: true
---
# Design Story Structure
Build a load-bearing narrative skeleton that keeps audiences emotionally engaged from page one to the final scene.
## Why This Is Best Practice
**Adopted by:** Hollywood development executives; MFA creative writing programs; game narrative designers at studios including BioWare and Naughty Dog
**Impact:** Blake Snyder's Save the Cat beat sheet is used across thousands of produced films; McKee's Story seminar has trained screenwriters whose films have earned over $2 billion at the box office
**Why best:** Audiences are wired to expect setup, escalation, and resolution. Structure is not a constraint on creativity — it is the invisible scaffolding that lets creativity land. Without it, even original ideas feel unsatisfying because they violate emotional expectations built by centuries of narrative tradition.
## Steps
1. **Identify the theme** — state in one sentence what the story is fundamentally about; every beat should test or prove this theme
2. **Define the protagonist's wound and want** — the external goal (want) drives plot; the internal need (wound) drives character; they must be in tension
3. **Place the inciting incident at 10-12%** — the event that disrupts the protagonist's ordinary world and poses the central dramatic question
4. **Design the break into act two at 25%** — the protagonist commits to pursuing the goal; no going back; the stakes become concrete
5. **Build midpoint reversal** — at the 50% mark, a false victory or false defeat that raises stakes and forces deeper commitment
6. **Write the dark night of the soul at 75%** — the protagonist's lowest point; they must choose to act from internal truth, not external pressure
7. **Land the climax and resolution** — the protagonist resolves the central conflict using skills or insight they lacked at the start; the wound is addressed
## Rules
- Every scene must advance plot, reveal character, or do both — never only one if the other is possible
- The protagonist must make the key climactic choice themselves; never resolve it through coincidence or a secondary character
- The theme must be dramatized, not stated by a character in dialogue
- Each act must end with a reversal that is surprising yet inevitable in retrospect
## Examples
**Theme:** Power corrupts those who believe they deserve it.
**Wound:** Protagonist was overlooked and undervalued.
**Want:** To become the most powerful person in the room.
**Result:** Every scene tests whether ambition can survive contact with integrity.
## Common Mistakes
- Starting with backstory instead of action: the inciting incident must arrive before the reader loses interest
- Resolving the external conflict without addressing the internal wound: the story feels hollow even if the plot resolves
- Writing a midpoint that is merely eventful rather than transformative: it must change what the story is about
## When NOT to Use
- Do not apply this skill to experimental or avant-garde literary fiction that deliberately subverts narrative convention, where imposing three-act beat positions would neutralize the formal disruption that constitutes the work's artistic statement.
- Do not use this skill for short fiction under 3,000 words, where the compressed form cannot accommodate the full structural arc and forcing beat-sheet percentages produces a rushed, mechanical feel rather than the tight unity a short story requires.
- Do not apply this skill to episodic narrative podcasts or serialized fiction where each episode must function as a standalone story, making a single overarching structural skeleton inappropriate without first designing the episode-level micro-structure separately.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!