{"owner":"Donchitos","repo":"Claude-Code-Game-Studios","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md"],"skills":{"CLAUDE.md":"# Claude Code Game Studios -- Game Studio Agent Architecture\n\nIndie game development managed through 49 coordinated Claude Code subagents.\nEach agent owns a specific domain, enforcing separation of concerns and quality.\n\n## Technology Stack\n\n- **Engine**: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]\n- **Language**: [CHOOSE: GDScript / C# / C++ / Blueprint]\n- **Version Control**: Git with trunk-based development\n- **Build System**: [SPECIFY after choosing engine]\n- **Asset Pipeline**: [SPECIFY after choosing engine]\n\n> **Note**: Engine-specialist agents exist for Godot, Unity, and Unreal with\n> dedicated sub-specialists. Use the set matching your engine.\n\n## Project Structure\n\n@.claude/docs/directory-structure.md\n\n## Engine Version Reference\n\n@docs/engine-reference/godot/VERSION.md\n\n## Technical Preferences\n\n@.claude/docs/technical-preferences.md\n\n## Coordination Rules\n\n@.claude/docs/coordination-rules.md\n\n## Collaboration Protocol\n\n**User-driven collaboration, not autonomous execution.**\nEvery task follows: **Question -> Options -> Decision -> Draft -> Approval**\n\n- Agents MUST ask \"May I write this to [filepath]?\" before using Write/Edit tools\n- Agents MUST show drafts or summaries before requesting approval\n- Multi-file changes require explicit approval for the full changeset\n- No commits without user instruction\n\nSee `docs/COLLABORATIVE-DESIGN-PRINCIPLE.md` for full protocol and examples.\n\n> **First session?** If the project has no engine configured and no game concept,\n> run `/start` to begin the guided onboarding flow.\n\n## Coding Standards\n\n@.claude/docs/coding-standards.md\n\n## Context Management\n\n@.claude/docs/context-management.md\n"},"files":{"CLAUDE.md":"# Claude Code Game Studios -- Game Studio Agent Architecture\n\nIndie game development managed through 49 coordinated Claude Code subagents.\nEach agent owns a specific domain, enforcing separation of concerns and quality.\n\n## Technology Stack\n\n- **Engine**: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]\n- **Language**: [CHOOSE: GDScript / C# / C++ / Blueprint]\n- **Version Control**: Git with trunk-based development\n- **Build System**: [SPECIFY after choosing engine]\n- **Asset Pipeline**: [SPECIFY after choosing engine]\n\n> **Note**: Engine-specialist agents exist for Godot, Unity, and Unreal with\n> dedicated sub-specialists. Use the set matching your engine.\n\n## Project Structure\n\n@.claude/docs/directory-structure.md\n\n## Engine Version Reference\n\n@docs/engine-reference/godot/VERSION.md\n\n## Technical Preferences\n\n@.claude/docs/technical-preferences.md\n\n## Coordination Rules\n\n@.claude/docs/coordination-rules.md\n\n## Collaboration Protocol\n\n**User-driven collaboration, not autonomous execution.**\nEvery task follows: **Question -> Options -> Decision -> Draft -> Approval**\n\n- Agents MUST ask \"May I write this to [filepath]?\" before using Write/Edit tools\n- Agents MUST show drafts or summaries before requesting approval\n- Multi-file changes require explicit approval for the full changeset\n- No commits without user instruction\n\nSee `docs/COLLABORATIVE-DESIGN-PRINCIPLE.md` for full protocol and examples.\n\n> **First session?** If the project has no engine configured and no game concept,\n> run `/start` to begin the guided onboarding flow.\n\n## Coding Standards\n\n@.claude/docs/coding-standards.md\n\n## Context Management\n\n@.claude/docs/context-management.md\n"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# Claude Code Game Studios -- Game Studio Agent Architecture\n\nIndie game development managed through 49 coordinated Claude Code subagents.\nEach agent owns a specific domain, enforcing separation of concerns and quality.\n\n## Technology Stack\n\n- **Engine**: [CHOOSE: Godot 4 / Unity / Unreal Engine 5]\n- **Language**: [CHOOSE: GDScript / C# / C++ / Blueprint]\n- **Version Control**: Git with trunk-based development\n- **Build System**: [SPECIFY after choosing engine]\n- **Asset Pipeline**: [SPECIFY after choosing engine]\n\n> **Note**: Engine-specialist agents exist for Godot, Unity, and Unreal with\n> dedicated sub-specialists. Use the set matching your engine.\n\n## Project Structure\n\n@.claude/docs/directory-structure.md\n\n## Engine Version Reference\n\n@docs/engine-reference/godot/VERSION.md\n\n## Technical Preferences\n\n@.claude/docs/technical-preferences.md\n\n## Coordination Rules\n\n@.claude/docs/coordination-rules.md\n\n## Collaboration Protocol\n\n**User-driven collaboration, not autonomous execution.**\nEvery task follows: **Question -> Options -> Decision -> Draft -> Approval**\n\n- Agents MUST ask \"May I write this to [filepath]?\" before using Write/Edit tools\n- Agents MUST show drafts or summaries before requesting approval\n- Multi-file changes require explicit approval for the full changeset\n- No commits without user instruction\n\nSee `docs/COLLABORATIVE-DESIGN-PRINCIPLE.md` for full protocol and examples.\n\n> **First session?** If the project has no engine configured and no game concept,\n> run `/start` to begin the guided onboarding flow.\n\n## Coding Standards\n\n@.claude/docs/coding-standards.md\n\n## Context Management\n\n@.claude/docs/context-management.md\n","category":"root","tokens":417}]}