narrative-story-structure-game

Use when designing interactive narratives, branching storylines, player agency systems, non-linear story structures, or act frameworks for games. Triggers: branching narrative, player agency, story arc, interactive story, dialogue.

6 stars

Best use case

narrative-story-structure-game is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when designing interactive narratives, branching storylines, player agency systems, non-linear story structures, or act frameworks for games. Triggers: branching narrative, player agency, story arc, interactive story, dialogue.

Teams using narrative-story-structure-game should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/story-structure-game/SKILL.md --create-dirs "https://raw.githubusercontent.com/fcsouza/agent-skills/main/plugins/game-dev/narrative/story-structure-game/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/story-structure-game/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How narrative-story-structure-game Compares

Feature / Agentnarrative-story-structure-gameStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when designing interactive narratives, branching storylines, player agency systems, non-linear story structures, or act frameworks for games. Triggers: branching narrative, player agency, story arc, interactive story, dialogue.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Story Structure for Games

## Purpose

Branching narratives, player agency, non-linear story structure, and act frameworks adapted for interactive media. Genre-agnostic — works for any game with narrative elements.

## When to Use

Trigger: story structure, branching narrative, player agency, non-linear story, act structure, story beats, narrative arc, dialogue tree, multiple endings, player choice, consequence system, narrative design

## Prerequisites

- `quest-narrative-coherence` — ensures all story content is consistent
- `worldbuilding` — provides the world context for the story

## Core Principles

> Hideo Kojima: "Games can tell stories that no other medium can — stories where the audience is the protagonist."
> Ken Levine: "Narrative should emerge from systems, not just scripted sequences."
> Hidetaka Miyazaki: "The best stories are the ones players piece together themselves."

1. **Player agency is sacred** — the player must feel their choices matter; never invalidate a meaningful decision
2. **Show consequences** — choices without visible consequences feel meaningless; show the impact
3. **Non-linear doesn't mean random** — structure the narrative so any path through it feels intentional
4. **Environmental storytelling first** — the world tells the story; dialogue and cutscenes support it (Miyazaki)
5. **Dramatic structure still applies** — even branching narratives need tension, climax, and resolution
6. **Multiple endings must all feel earned** — no "good ending" and "bad ending"; each ending should reflect the player's journey
7. **Pacing is controlled by the player** — design for players who rush AND players who explore

## Narrative Frameworks

### Three-Act Structure (Adapted for Games)
```
Act 1 — Setup (10-20% of game)
  Hook → World introduction → Inciting incident → Player given agency

Act 2 — Confrontation (60-70% of game)
  Rising challenges → Major choices → Consequences compound → Midpoint twist

Act 3 — Resolution (10-20% of game)
  Climax → Final choice → Resolution shaped by prior decisions → Denouement
```

### Branching Narrative Model
```
         [Start]
        /       \
    [Choice A] [Choice B]
      /    \      \
  [A1]    [A2]  [B1]
    \      |     /
     [Convergence Point]
        /       \
   [Final A]  [Final B]
```

### Kishōtenketsu (Eastern Structure — No Conflict Required)
```
Ki (Introduction) → Shō (Development) → Ten (Twist/Revelation) → Ketsu (Conclusion)
```

## Cross-References

- `quest-narrative-coherence` — story consistency validation
- `worldbuilding` — world context
- `character-design-narrative` — character arcs within the story
- `quest-mission-design` — quests as story delivery mechanism

## Pitfalls & Anti-Patterns

- **"Illusion of choice"** — choices that all lead to the same outcome; players notice and feel cheated
- **"Ludonarrative dissonance"** — gameplay contradicts the story (hero kills 500 people then mourns one death)
- **"Cutscene prison"** — long non-interactive sequences that remove player agency
- **"Exposition dump"** — characters explaining plot instead of showing it
- **"Disconnected side stories"** — narrative content that feels irrelevant to the main arc

## Designer Philosophy

**Hideo Kojima** (Metal Gear Solid): Games have a unique narrative advantage — the player IS the character. Use this. Break the fourth wall. Make the player's real-world actions part of the story. The controller, the save file, the screen itself can all be narrative tools.

**Ken Levine** (BioShock): "Would you kindly" works because it uses game mechanics as narrative. The best game stories are inseparable from the gameplay — they can't be a movie, they can't be a book. They can ONLY be a game.

**Hidetaka Miyazaki** (Dark Souls): Not every player needs to understand the story. Layer narrative so casual players get the broad strokes, and dedicated players who read item descriptions and explore every corner find a deeper, richer story beneath.

## Sources

- "Narrative Design for Indie Games" — GDC 2020
- "Writing for Games" — GDC 2018
- "The Art of Game Design" — Jesse Schell, Chapters on Story
- "Interactive Storytelling" — Chris Crawford
- "Designing BioShock's Narrative" — Ken Levine, GDC 2014

Related Skills

game-lore

6
from fcsouza/agent-skills

Adds or updates a single world lore entry (faction, location, NPC, or event) — validates against existing lore for consistency, applies the right template, and updates docs/world-lore.md. Extract the entry type (faction/location/npc/event) and name from the user's message.

game-expand

6
from fcsouza/agent-skills

Adds a new feature to an existing MVP plan — scoped architect interview, scope validation against original plan, and integration into the build sequence. Extract the feature name or description from the user's message. Requires docs/mvp-first-draft.md — run game-architect first.

game-build

6
from fcsouza/agent-skills

Builds a game component from the MVP plan — production TypeScript + Vitest tests + mock dependencies + build registry tracking. Extract the component name from the user's message (or "status" to check progress). Requires docs/mvp-first-draft.md — run game-architect first.

game-balance

6
from fcsouza/agent-skills

Analyzes a game system against design principles — economy health metrics, difficulty curve, reward schedules, and progression cost curves. Flags imbalances with severity levels. Use after creating an MVP plan with game-architect. Extract the analysis scope (economy/difficulty/progression/rewards/all) from the user's message.

game-architect

6
from fcsouza/agent-skills

Comprehensive game MVP interviewer and planner. Interviews you in progressive groups, researches genre conventions and reference games, then produces an actionable MVP First Draft with starter project files. Use when starting a new game project from scratch.

narrative-worldbuilding

6
from fcsouza/agent-skills

Use when creating game worlds, lore, factions, geography, timelines, or establishing world consistency rules. Genre-agnostic — works for fantasy, sci-fi, modern, or abstract settings. Triggers: lore, factions, geography, world bible, world creation.

narrative-quest-narrative-coherence

6
from fcsouza/agent-skills

Use when creating any quest, mission, or story content — enforces the 5-step narrative coherence check: lore validation, conflict detection, quest registry, and contradiction prevention. Triggers: coherence check, lore validation, quest registry, narrative consistency.

narrative-character-design-narrative

6
from fcsouza/agent-skills

Use when creating game characters, NPCs, character arcs, dialogue systems, archetypes, or character bibles. Triggers: character, NPC, dialogue, archetype, character bible, motivation arc.

infrastructure-monitoring-game-ops

6
from fcsouza/agent-skills

Use when implementing game monitoring, structured logging, player telemetry, alerting rules, or performance budgets. Triggers: monitoring, logging, telemetry, alerts, observability, metrics.

infrastructure-cursor-codex-integration

6
from fcsouza/agent-skills

Use when configuring Cursor IDE or OpenAI Codex for game development — .cursorrules files, prompt conventions, context injection. Triggers: cursor, .cursorrules, codex, IDE setup.

infrastructure-claude-code-game-workflow

6
from fcsouza/agent-skills

Use when starting a game project, choosing which skill to read, or navigating the game-dev skill ecosystem. Entry point for AI agents working on game development. Triggers: workflow, which skill, how to start, game project setup.

infrastructure-ci-cd-game

6
from fcsouza/agent-skills

Use when setting up CI/CD pipelines, GitHub Actions workflows, deployment automation, migration safety, or staging environments for game projects. Triggers: CI/CD, GitHub Actions, deployment, pipeline, staging.