core-loop-generate

Core Loop Generator

Generate the Core Loop phase (Phase 1) documents from a previously gathered context file. This skill runs with clean context and is non-interactive — all questions were answered during the gather phase.

Input

$ARGUMENTS

Parse Arguments

Extract from $ARGUMENTS:

• Context File: First non-flag argument (e.g., docs/game-design-bible/context/core-loop-context.md)
• Output Directory: --output-dir <path> (default: derived from context file's Bible Directory, i.e., <bible-dir>/01-core-loop/)

Source Integrity Rules

Every factual claim in these documents must be traceable to the context file.

1. Ground every claim. Every design statement must trace back to a specific entry in the context file (user answers, pillar definitions, concept context, or web research with URLs).
2. Flag ungrounded claims. If you need to state something not in the context file, mark it explicitly as [ASSUMPTION] in the document.
3. Never invent details. If the context file doesn't cover something, put it in Open Questions — don't fabricate.

Process

Step 1: Read Context and Pillars

1. Read the context file at the path provided in $ARGUMENTS.
2. Read <bible-dir>/DESIGN-PILLARS.md (derive bible-dir from the context file's Bible Directory field).
3. Extract:
   • Core Action, Feedback, Rewards, Motivation, Session Structure
   • All design pillars with definitions
   • Concept context (genre, platform, audience)
   • Web research findings
   • Open questions

Step 2: Create Output Directory

mkdir -p <output-dir>

Use Glob to verify <output-dir> exists.

Step 3: Generate core-loop.md

Write <output-dir>/core-loop.md following this structure:

# Core Loop — [Game Name]

> Pillar Alignment: [list which pillars this document serves]

## Overview

[1 paragraph summarizing the core gameplay loop — what the player does, why it's compelling, and how it serves the design pillars]

## The Loop

┌─────────────┐ │ ACTION │ ← [core verb(s)] └──────┬──────┘ ▼ ┌─────────────┐ │ FEEDBACK │ ← [how game responds] └──────┬──────┘ ▼ ┌─────────────┐ │ REWARD │ ← [what player gets] └──────┬──────┘ ▼ ┌─────────────┐ │ MOTIVATION │ ← [why player repeats] └──────┬──────┘ │ └──────→ back to ACTION

## Action

[Detailed description of the core player action(s). What does the player physically do — inputs, decisions, moment-to-moment choices. Ground in context file's Core Action section.]

### Input Vocabulary

[What buttons/gestures/commands does the player use? How does the action space evolve over time?]

## Feedback

[How the game communicates results back to the player. Visual, audio, haptic, systemic responses. Include 2-3 concrete examples from the context file.]

### Feedback Channels

| Channel | Example | Timing |
|---------|---------|--------|
| Visual | [example] | [immediate/delayed] |
| Audio | [example] | [immediate/delayed] |
| Systemic | [example] | [immediate/delayed] |

## Reward

[What the player earns or unlocks. Distinguish immediate from delayed rewards. Explain how rewards create the "one more turn" hook.]

### Reward Schedule

| Reward | Type | Frequency | Purpose |
|--------|------|-----------|---------|
| [reward] | [immediate/delayed] | [per action/per session/milestone] | [engagement hook/progression/mastery] |

## Motivation

[Why the player returns to the loop. Primary motivational driver and how the loop stays fresh over time. How does complexity layer? Does the context change?]

### Freshness Mechanisms

[How the loop avoids becoming stale — new challenges, evolving systems, social dynamics, content variety]

## Session Structure

[How a play session flows from start to finish]

### Session Start
[How the player enters the loop — menu flow, world entry, resumption of progress]

### Session Flow
[The middle — what the flow state looks like, how long the player stays engaged]

### Session End
[Natural stopping points vs. "just one more" hooks. How the game handles save/quit]

### Estimated Session Length
[Target session duration based on platform and genre context]

## Pillar Validation

[For EACH design pillar, explicitly state how the core loop serves it. Flag any pillar that is NOT served by the loop.]

| Pillar | Served By | How |
|--------|-----------|-----|
| [pillar name] | [which loop element(s)] | [specific explanation] |

**Gaps:** [List any pillars not served by the core loop. These MUST be addressed by later phases or flagged as design risks.]

## Design Rationale

[Why this loop was chosen over alternatives. Reference web research findings for genre conventions and known pitfalls. Cite URLs from context file.]

## Open Questions

- [Anything unresolved from the context file, plus new questions that emerged during generation]

## Cross-References

- **Design Pillars:** [path to DESIGN-PILLARS.md]
- **Concept:** [paths to 00-concept/ files]
- **Prototype Spec:** [path to prototype-spec.md]
- **Context File:** [path to context file]

## Changelog

| Date | Change | Author |
|------|--------|--------|
| [today] | Initial creation from context gathering | Claude |