Skip to content

Latest commit

 

History

History
56 lines (35 loc) · 1.75 KB

File metadata and controls

56 lines (35 loc) · 1.75 KB

Opencode Game Studios -- Game Studio Agent Architecture

Indie game development managed through 54 coordinated Opencode subagents. Each agent owns a specific domain, enforcing separation of concerns and quality.

Technology Stack

  • Engine: [CHOOSE: Godot 4 / Unity / Unreal Engine 5 / GameMaker Studio 2]
  • Language: [CHOOSE: GDScript / C# / C++ / Blueprint / GML]
  • 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, Unreal, and GameMaker with dedicated sub-specialists. Use the set matching your engine.

Project Structure

@.opencode/docs/directory-structure.md

Engine Version Reference

@docs/engine-reference/godot/VERSION.md @docs/engine-reference/unity/VERSION.md @docs/engine-reference/gamemaker/VERSION.md

Technical Preferences

@.opencode/docs/technical-preferences.md

Coordination Rules

@.opencode/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

@.opencode/docs/coding-standards.md

Context Management

@.opencode/docs/context-management.md