Pacing and the player journey

Skill rondorkerin/gamestack/plugins/gamestack/skills/pacing-and-the-player-journey

The game-design process for Claude — knowledge + workflow skills for designing games, tuned for headless, procedural, AI-authored development (engine-agnostic; Godot).

Install

npx -y skills add rondorkerin/gamestack --skill pacing-and-the-player-journey

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when designing, auditing, or generating the macro arc of an experience — how engagement rises and falls across an encounter, a session, a level, and an entire playthrough. Covers the interest curve and fractal pacing, tension/rest rhythm, novelty cadence and mid-game sag, nested engagement loops and retention ethics, first-hour pacing by genre, and the procedural pacing director algorithm. Triggers on "pacing", "tension curve", "interest curve", "the game drags", "mid-game sag", "player journey", "intensity", "rest beats", "novelty pacing", "retention loop", "the game feels monotonous", "pacing director", "flow state", "pacing director algorithm", "engagement arc", "first hour", "tutorial pacing", "appointment mechanics", "compulsion loop", "safe room", "breathing room", "climax and denouement", "new toy cadence", "encounter pacing".

SKILL.md

4.0 KB, as published. Nobody here has run it

Pacing & the Player Journey

How to engineer engagement across time — from the second-to-second tension of a single encounter up through the full-playthrough arc — using the interest curve, deliberate rest, and a pacing director that governs generated intensity.

Tier: universal craft (→ gamestack-core). Applies to every genre and every game. The second-to-second feel of an individual action lives in game-feel-and-juice, which cites up to this skill for the macro layer.

When to use this

Authoring or auditing a playthrough-scale intensity graph (the macro arc)
Diagnosing why a session feels flat, exhausting, or like a treadmill
Scheduling novelty introduction to prevent the mid-game sag
Designing retention loops and auditing them for ethical coercion
Speccing the first-hour sequence for a new genre or game
Designing or implementing a procedural pacing director for generated content

Scope

This skill owns the macro arc — pacing across encounter, level, session, and playthrough. Adjacent concerns live in sibling skills:

Second-to-second action feel, juice, hit-stop, camera → game-feel-and-juice (this skill is the layer above it)
Spatial pacing in open worlds — landmark density, zone gradient → open-world-design
In-level encounter and room sequencing → level-design
Encounter intensity and telegraphing within a fight → combat-design
The flow/motivation theory underneath (Csikszentmihalyi) → game-design-fundamentals
Narrative beat structure, quest hooks, story arcs → narrative-and-quest-design
Procedurally generating the content the pacing director schedules → procedural-generation, procgen-review

How the pieces fit

GUIDE.md — the cited why, in six sub-domains: the intensity/interest curve (Schell's fractal rule, hook, climax); challenge & rest rhythm (tension/release, the rest-beat toolbox, latent tension); novelty pacing and the mid-game sag (new-toy schedule, teach-test-twist); nested loops and retention ethics (four-loop model, loop-arc integration, appointment mechanics, the ethics line); first-hour pacing by genre; and the pacing director algorithm (L4D, Warframe, generalized pseudocode). Each rule carries an exemplar + source, a Test for: criterion, a named failure mode, and a procedural / headless implication. Includes full spec-level pacing director pseudocode.
CHECKLIST.md — Do/Don't + machine-enforceable Test-for criteria, grouped by sub-domain, plus headless guardrails for generated-content pipelines.

The one idea to anchor on

The interest curve is fractal — the same tension/rest shape must hold at encounter, level, session, and playthrough scale simultaneously. A fight that ends with no wind-down, a level with no safe room, a session with no hook for the next play, a game whose climax undershoots its mid-act set-piece: all are the same structural failure at different zoom levels. Build a pacing director that schedules intensity across all four scales at once and enforces a relax window after every peak. The curve is not a metaphor — graph it.

Start with GUIDE.md, then apply CHECKLIST.md.