gds-game-architecture

Designs game architecture decisions covering engines, networking, and implementation patterns through guided steps.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-game-architecture-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-game-architecture
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-game-architecture
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-game-architecture-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects built by AI agents often fail because architectural decisions are made inconsistently or left implicit. This Skill runs a structured, step-by-step workflow that produces a complete architecture document — engine selection, networking model, physics, save systems, and implementation patterns — so every AI agent implements against the same decisions. ## Core Features & Use Cases - Guided Decision Workflow: Walks through sequential step files covering engine choice, rendering, physics, networking, input, AI, persistence, and deployment, with a decision catalog mapping requirements to compatible technology stacks. - Engine-Specific Knowledge: Loads deep knowledge fragments for Godot, Unity, Unreal, Phaser, or Roblox only for the selected engine, plus a catalog of MCP servers that give AI agents direct editor access. - Validation Checklist: Ships a checklist that verifies decision completeness, version specificity, starter template integration, and AI-agent implementability before coding begins. - Use Case: A solo developer planning a multiplayer roguelike uses this Skill to decide between Godot and Unity, select a netcode model, define save schema conventions, and produce an architecture document that coding agents follow without ambiguity. ## Quick Start Ask the AI to design the game architecture for your project by describing your game concept and target platforms.

Frequently Asked Questions about gds-game-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a game architecture document for AI agents?

Run this workflow, which walks through sequential decision steps covering engine, rendering, networking, physics, and persistence. It outputs an architecture document with a decision summary table, project structure, and implementation patterns that AI coding agents follow consistently.

How do I choose between Unity, Unreal, and Godot for my game?

The decision catalog maps requirements to engines: Unreal for high-fidelity 3D, Godot for 2D or open-source priority, Unity for cross-platform mobile. Engine-specific knowledge fragments then provide deeper guidance on the selected engine's architecture patterns.

What MCP servers are available for game engines?

The engine-mcps catalog lists MCP servers per engine: mcp-unity and CoplayDev for Unity, unreal-mcp for Unreal, GoPeak and others for Godot, and the official Roblox Studio MCP. These let AI agents inspect scenes, edit scripts, and run playtests directly.

Does this workflow support multiplayer game architecture?

Yes, the architecture patterns file covers real-time multiplayer, turn-based, and MMO-scale networking with decisions for server authority, state synchronization, lag compensation, and matchmaking, plus suggested technology stacks for each model.

When should I not use Godot for a game project?

Avoid Godot when AAA-quality 3D visuals are required, console launch is a hard requirement (console export needs paid third-party porting), or VR is the primary platform. The Godot knowledge fragment details these limitations and console export realities.