mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 04:51:46 +00:00

Files

Donchitos ad540fe75d Game Studio Agent Architecture — complete setup (Phases 1-7)

48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-13 21:04:24 +11:00

1.5 KiB

Raw Blame History

paths

prototypes/**

Prototype Code Standards (Relaxed)

Prototypes are throwaway code for validating ideas. Standards are intentionally relaxed to maximize iteration speed. The goal is learning, not production quality.

What's Allowed in Prototypes

Hardcoded values (no need for data-driven config)
Minimal or no doc comments
Simple architecture (no dependency injection required)
Singletons and global state
Copy-pasted code (no need for abstraction)
Debug output left in place
Placeholder art and audio
Quick-and-dirty solutions

What's Still Required

Each prototype lives in its own subdirectory: prototypes/[name]/
Every prototype MUST have a README.md with:
- What hypothesis is being tested
- How to run the prototype
- Current status (in-progress / concluded)
- Findings (updated when prototype concludes)
No production code may reference or import from prototypes/
Prototypes must not modify files outside prototypes/
Prototypes must not be deployed or shipped

When a Prototype Succeeds

If a prototype validates a concept and the feature moves to production:

The prototype code is NOT migrated directly — it is rewritten to production standards
The prototype README.md findings inform the production design document
The prototype directory is preserved for reference but never extended

Cleanup

Concluded prototypes should be archived or deleted after findings are captured. Never let prototype code grow into production code through incremental "cleanup."

1.5 KiB Raw Blame History