mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
e289ce906f
* Add context resilience: file-backed state, incremental writing, auto-recovery Prevents "prompt too long" crashes from killing sessions by persisting work to disk incrementally instead of relying on conversation memory. Changes: - pre-compact.sh: dumps session state before context compression - session-start.sh: detects active.md for crash recovery - session-stop.sh: archives and clears active.md on clean shutdown - context-management.md: file-backed state as primary strategy - 9 agents updated with incremental section writing protocol (game-designer, systems-designer, economy-designer, narrative-director, level-designer, world-builder, writer, art-director, audio-director) - CLAUDE.md: trimmed redundant imports (10 → 5) to reduce token overhead - design-docs.md rule: enforces incremental writing pattern - .gitignore: excludes ephemeral session state files - directory-structure.md: documents session-state/ and session-logs/ - COLLABORATIVE-DESIGN-PRINCIPLE.md: documents incremental writing pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add AskUserQuestion integration across collaborative protocols Explicitly reference the AskUserQuestion tool in all collaborative agent definitions, protocol templates, team orchestrator skills, and the master principle doc. Introduces the Explain-then-Capture pattern: agents write full expert analysis in conversation, then call AskUserQuestion with concise labels to capture decisions via structured UI. 26 files updated: - 3 protocol templates (design, leadership, implementation) - 14 agent definitions (10 design + 3 leadership + writer) - 8 orchestrator skills (brainstorm + 7 team-*) - 1 master principle doc (COLLABORATIVE-DESIGN-PRINCIPLE.md) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add /design-systems skill: concept-to-GDD decomposition workflow Bridges the gap between game concept and per-system design documents. Professional studios use systems enumeration + dependency sorting between concept and feature docs — skipping this step is one of the most expensive mistakes (systems discovered during production cost 5-10x more to add). New files: - .claude/skills/design-systems/SKILL.md — 7-phase orchestration skill (enumerate systems, map dependencies, assign priorities, write GDDs) - .claude/docs/templates/systems-index.md — master tracking template Flow integration (7 existing skills updated): - brainstorm, start, setup-engine, design-review, gate-check, project-stage-detect, game-concept template all reference /design-systems at the appropriate workflow touchpoints Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix cross-platform bugs, add missing tool permissions, and update docs for v0.2.0 Hooks: fix \s → [[:space:]] in grep -E fallbacks (3 files), fix detect-gaps.sh empty-variable bug, fix log-agent.sh field name (agent_name → agent_type), harden validate-push.sh with explicit $MATCHED_BRANCH, convert for-in loops to while-read for space-safe iteration, add POSIX head -n syntax, increase PreCompact timeout, widen session-stop log window. Skills: add AskUserQuestion to 10 skills and TodoWrite to 8 multi-phase skills. Fix project-stage-detect template/output paths, tech-artist → technical-artist. Docs: add /design-systems to all references (README, quick-start, workflow guide, skills-reference), update skill count 35 → 36, remove stale AI artifacts from COLLABORATIVE-DESIGN-PRINCIPLE.md, add AskUserQuestion note to examples README. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
68 lines
3.6 KiB
Markdown
68 lines
3.6 KiB
Markdown
---
|
|
name: team-narrative
|
|
description: "Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design."
|
|
argument-hint: "[narrative content description]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite
|
|
---
|
|
When this skill is invoked, orchestrate the narrative team through a structured pipeline.
|
|
|
|
**Decision Points:** At each phase transition, use `AskUserQuestion` to present
|
|
the user with the subagent's proposals as selectable options. Write the agent's
|
|
full analysis in conversation, then capture the decision with concise labels.
|
|
The user must approve before moving to the next phase.
|
|
|
|
## Team Composition
|
|
- **narrative-director** — Story arcs, character design, dialogue strategy, narrative vision
|
|
- **writer** — Dialogue writing, lore entries, item descriptions, in-game text
|
|
- **world-builder** — World rules, faction design, history, geography, environmental storytelling
|
|
- **level-designer** — Level layouts that serve the narrative, pacing, environmental storytelling beats
|
|
|
|
## How to Delegate
|
|
|
|
Use the Task tool to spawn each team member as a subagent:
|
|
- `subagent_type: narrative-director` — Story arcs, character design, narrative vision
|
|
- `subagent_type: writer` — Dialogue writing, lore entries, in-game text
|
|
- `subagent_type: world-builder` — World rules, faction design, history, geography
|
|
- `subagent_type: level-designer` — Level layouts that serve the narrative, pacing
|
|
|
|
Always provide full context in each agent's prompt (narrative brief, lore dependencies, character profiles). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 2 agents can run simultaneously).
|
|
|
|
## Pipeline
|
|
|
|
### Phase 1: Narrative Direction
|
|
Delegate to **narrative-director**:
|
|
- Define the narrative purpose of this content: what story beat does it serve?
|
|
- Identify characters involved, their motivations, and how this fits the overall arc
|
|
- Set the emotional tone and pacing targets
|
|
- Specify any lore dependencies or new lore this introduces
|
|
- Output: narrative brief with story requirements
|
|
|
|
### Phase 2: World Foundation (parallel)
|
|
Delegate in parallel:
|
|
- **world-builder**: Create or update lore entries for factions, locations, and history relevant to this content. Cross-reference against existing lore for contradictions. Set canon level for new entries.
|
|
- **writer**: Draft character dialogue using voice profiles. Ensure all lines are under 120 characters, use named placeholders for variables, and are localization-ready.
|
|
|
|
### Phase 3: Level Narrative Integration
|
|
Delegate to **level-designer**:
|
|
- Review the narrative brief and lore foundation
|
|
- Design environmental storytelling elements in the level
|
|
- Place narrative triggers, dialogue zones, and discovery points
|
|
- Ensure pacing serves both gameplay and story
|
|
|
|
### Phase 4: Review and Consistency
|
|
Delegate to **narrative-director**:
|
|
- Review all dialogue against character voice profiles
|
|
- Verify lore consistency across new and existing entries
|
|
- Confirm narrative pacing aligns with level design
|
|
- Check that all mysteries have documented "true answers"
|
|
|
|
### Phase 5: Polish
|
|
- Writer reviews all text for localization readiness
|
|
- Verify no line exceeds dialogue box constraints
|
|
- Confirm all text uses string keys (localization pipeline ready)
|
|
- World-builder finalizes canon levels for all new lore
|
|
|
|
## Output
|
|
A summary report covering: narrative brief status, lore entries created/updated, dialogue lines written, level narrative integration points, consistency review results, and any unresolved contradictions.
|