mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
4425d473ea
New users no longer get pushed toward /setup-engine before they even have a game idea. The /start skill asks where they are (no idea, vague idea, clear concept, existing work) and routes to the right workflow. The detect-gaps hook now detects fresh projects and suggests /start. All docs updated: README, quick-start, workflow guide, skills/hooks references, CLAUDE.md (skill count 34→35). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
73 lines
1.9 KiB
Markdown
73 lines
1.9 KiB
Markdown
# Claude Code Game Studios -- Game Studio Agent Architecture
|
|
|
|
Indie game development managed through 48 coordinated Claude Code subagents.
|
|
Each agent owns a specific domain, enforcing separation of concerns and quality.
|
|
|
|
## Technology Stack
|
|
|
|
- **Engine**: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]
|
|
- **Language**: [CHOOSE: GDScript / C# / C++ / Blueprint]
|
|
- **Version Control**: Git with trunk-based development
|
|
- **Build System**: [SPECIFY after choosing engine]
|
|
- **Asset Pipeline**: [SPECIFY after choosing engine]
|
|
|
|
> **Note**: Engine-specialist agents exist for Godot, Unity, and Unreal with
|
|
> dedicated sub-specialists. Use the set matching your engine.
|
|
|
|
## Project Structure
|
|
|
|
@.claude/docs/directory-structure.md
|
|
|
|
## Engine Version Reference
|
|
|
|
@docs/engine-reference/godot/VERSION.md
|
|
|
|
## Technical Preferences
|
|
|
|
@.claude/docs/technical-preferences.md
|
|
|
|
## Agent Roster
|
|
|
|
@.claude/docs/agent-roster.md
|
|
|
|
## Coordination Rules
|
|
|
|
@.claude/docs/coordination-rules.md
|
|
|
|
## Collaboration Protocol
|
|
|
|
**User-driven collaboration, not autonomous execution.**
|
|
Every task follows: **Question -> Options -> Decision -> Draft -> Approval**
|
|
|
|
- Agents MUST ask "May I write this to [filepath]?" before using Write/Edit tools
|
|
- Agents MUST show drafts or summaries before requesting approval
|
|
- Multi-file changes require explicit approval for the full changeset
|
|
- No commits without user instruction
|
|
|
|
See `docs/COLLABORATIVE-DESIGN-PRINCIPLE.md` for full protocol and examples.
|
|
|
|
> **First session?** If the project has no engine configured and no game concept,
|
|
> run `/start` to begin the guided onboarding flow.
|
|
|
|
## Coding Standards & Review
|
|
|
|
@.claude/docs/coding-standards.md
|
|
|
|
@.claude/docs/review-workflow.md
|
|
|
|
## Context Management
|
|
|
|
@.claude/docs/context-management.md
|
|
|
|
## Active Hooks
|
|
|
|
@.claude/docs/hooks-reference.md
|
|
|
|
## Available Skills (Slash Commands)
|
|
|
|
@.claude/docs/skills-reference.md
|
|
|
|
## Path-Specific Rules
|
|
|
|
@.claude/docs/rules-reference.md
|