Game Story World Character
Use this skill to make narrative and world design serve play instead of competing with it. The output should give the coding agent clear content structures, state needs, triggers, and constraints.
Source Traceability
Primary source: The Art of Game Design: A Book of Lenses, Third Edition by Jesse Schell, especially chapters 17-23 on story, indirect control, worlds, characters, spaces, presence, and aesthetics. The workflow is transformed and paraphrased.
Supporting source: MDA for separating authored mechanics from player-experienced dynamics and aesthetics.
Workflow
- Define the role of story: premise, motivation, context, consequence, mystery, comedy, identity, or emotional payoff.
- Align story beats with player action and system state.
- Use indirect control through goals, affordances, layout, rewards, information, and character cues.
- Specify world rules, character functions, spaces, mood, and aesthetic constraints.
- Convert narrative intent into implementable triggers, content schema, and test cases.
Required Output
Narrative Function: why the game needs story or world detail.Story-Gameplay Map: beats tied to player actions and system state.World Rules: facts, boundaries, tone, and contradictions to avoid.Character Specs: role, desire, behavior hooks, dialogue constraints, and gameplay purpose.Implementation Notes: state flags, triggers, content data, level cues, and tests.
Local References
Before producing a story/world spec, read:
references/core/guide.mdworkflows/narrative-systems-spec.md
1---2name: game-story-world-character3description: Design or evaluate game story, world, characters, spaces, presence, aesthetics, and indirect control. Use when adding narrative, quests, levels, environments, character arcs, worldbuilding, environmental storytelling, or emotional context to gameplay.4license: MIT5---67# Game Story World Character89Use this skill to make narrative and world design serve play instead of competing with it. The output should give the coding agent clear content structures, state needs, triggers, and constraints.1011## Source Traceability1213Primary source: *The Art of Game Design: A Book of Lenses, Third Edition* by Jesse Schell, especially chapters 17-23 on story, indirect control, worlds, characters, spaces, presence, and aesthetics. The workflow is transformed and paraphrased.1415Supporting source: MDA for separating authored mechanics from player-experienced dynamics and aesthetics.1617## Workflow18191. Define the role of story: premise, motivation, context, consequence, mystery, comedy, identity, or emotional payoff.202. Align story beats with player action and system state.213. Use indirect control through goals, affordances, layout, rewards, information, and character cues.224. Specify world rules, character functions, spaces, mood, and aesthetic constraints.235. Convert narrative intent into implementable triggers, content schema, and test cases.2425## Required Output2627- `Narrative Function`: why the game needs story or world detail.28- `Story-Gameplay Map`: beats tied to player actions and system state.29- `World Rules`: facts, boundaries, tone, and contradictions to avoid.30- `Character Specs`: role, desire, behavior hooks, dialogue constraints, and gameplay purpose.31- `Implementation Notes`: state flags, triggers, content data, level cues, and tests.3233## Local References3435Before producing a story/world spec, read:3637- `references/core/guide.md`38- `workflows/narrative-systems-spec.md`
ConcertoNotes