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>
77 lines
2.9 KiB
Markdown
77 lines
2.9 KiB
Markdown
---
|
|
name: design-review
|
|
description: "Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers."
|
|
argument-hint: "[path-to-design-doc]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep
|
|
---
|
|
|
|
When this skill is invoked:
|
|
|
|
1. **Read the target design document** in full.
|
|
|
|
2. **Read the master CLAUDE.md** to understand project context and standards.
|
|
|
|
3. **Read related design documents** referenced or implied by the target doc
|
|
(check `design/gdd/` for related systems).
|
|
|
|
4. **Evaluate against the Design Document Standard checklist**:
|
|
- [ ] Has Overview section (one-paragraph summary)
|
|
- [ ] Has Player Fantasy section (intended feeling)
|
|
- [ ] Has Detailed Rules section (unambiguous mechanics)
|
|
- [ ] Has Formulas section (all math defined with variables)
|
|
- [ ] Has Edge Cases section (unusual situations handled)
|
|
- [ ] Has Dependencies section (other systems listed)
|
|
- [ ] Has Tuning Knobs section (configurable values identified)
|
|
- [ ] Has Acceptance Criteria section (testable success conditions)
|
|
|
|
5. **Check for internal consistency**:
|
|
- Do the formulas produce values that match the described behavior?
|
|
- Do edge cases contradict the main rules?
|
|
- Are dependencies bidirectional (does the other system know about this one)?
|
|
|
|
6. **Check for implementability**:
|
|
- Are the rules precise enough for a programmer to implement without guessing?
|
|
- Are there any "hand-wave" sections where details are missing?
|
|
- Are performance implications considered?
|
|
|
|
7. **Check for cross-system consistency**:
|
|
- Does this conflict with any existing mechanic?
|
|
- Does this create unintended interactions with other systems?
|
|
- Is this consistent with the game's established tone and pillars?
|
|
|
|
8. **Output the review** in this format:
|
|
|
|
```
|
|
## Design Review: [Document Title]
|
|
|
|
### Completeness: [X/8 sections present]
|
|
[List missing sections]
|
|
|
|
### Consistency Issues
|
|
[List any internal or cross-system contradictions]
|
|
|
|
### Implementability Concerns
|
|
[List any vague or unimplementable sections]
|
|
|
|
### Balance Concerns
|
|
[List any obvious balance risks]
|
|
|
|
### Recommendations
|
|
[Prioritized list of improvements]
|
|
|
|
### Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]
|
|
```
|
|
|
|
9. **Contextual next step recommendations**:
|
|
- If the document being reviewed is `game-concept.md` or `game-pillars.md`:
|
|
- Check if `design/gdd/systems-index.md` exists
|
|
- If it does NOT exist, add to Recommendations:
|
|
> "This concept is ready for systems decomposition. Run `/design-systems`
|
|
> to break it down into individual systems with dependencies and priorities,
|
|
> then write per-system GDDs."
|
|
- If the document is an individual system GDD:
|
|
- Check if the systems index references this system
|
|
- If so, suggest updating its status: "Update the systems index status for
|
|
this system from 'In Design' to 'Designed'."
|