mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
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>
This commit is contained in:
46
.claude/rules/data-files.md
Normal file
46
.claude/rules/data-files.md
Normal file
@@ -0,0 +1,46 @@
|
||||
---
|
||||
paths:
|
||||
- "assets/data/**"
|
||||
---
|
||||
|
||||
# Data File Rules
|
||||
|
||||
- All JSON files must be valid JSON — broken JSON blocks the entire build pipeline
|
||||
- File naming: lowercase with underscores only, following `[system]_[name].json` pattern
|
||||
- Every data file must have a documented schema (either JSON Schema or documented in the corresponding design doc)
|
||||
- Numeric values must include comments or companion docs explaining what the numbers mean
|
||||
- Use consistent key naming: camelCase for keys within JSON files
|
||||
- No orphaned data entries — every entry must be referenced by code or another data file
|
||||
- Version data files when making breaking schema changes
|
||||
- Include sensible defaults for all optional fields
|
||||
|
||||
## Examples
|
||||
|
||||
**Correct** naming and structure (`combat_enemies.json`):
|
||||
|
||||
```json
|
||||
{
|
||||
"goblin": {
|
||||
"baseHealth": 50,
|
||||
"baseDamage": 8,
|
||||
"moveSpeed": 3.5,
|
||||
"lootTable": "loot_goblin_common"
|
||||
},
|
||||
"goblin_chief": {
|
||||
"baseHealth": 150,
|
||||
"baseDamage": 20,
|
||||
"moveSpeed": 2.8,
|
||||
"lootTable": "loot_goblin_rare"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Incorrect** (`EnemyData.json`):
|
||||
|
||||
```json
|
||||
{
|
||||
"Goblin": { "hp": 50 }
|
||||
}
|
||||
```
|
||||
|
||||
Violations: uppercase filename, uppercase key, no `[system]_[name]` pattern, missing required fields.
|
||||
Reference in New Issue
Block a user