Individual skill

game-story-world-character

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.

plugins/LVTD-LLC/skills/skills/game-story-world-character/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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

1. Define the role of story: premise, motivation, context, consequence, mystery, comedy, identity, or emotional payoff.
2. Align story beats with player action and system state.