gds-game-architecture

Design game architecture decisions covering engines, networking, and implementation patterns through a guided workflow.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-game-architecture-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-game-architecture
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-game-architecture
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-game-architecture-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects stall when architectural decisions are made ad hoc, causing AI agents and developers to implement conflicting patterns. This Skill walks you through a structured, step-by-step discovery process to produce a complete architecture document covering engine selection, systems design, networking, and consistency rules. ## Core Features & Use Cases - Guided Decision Workflow: Sequential step files lead you through engine selection, rendering, physics, networking, save systems, and deployment decisions with a decision catalog and architecture pattern matching. - Engine-Specific Knowledge: Loads deep knowledge fragments for Godot, Unity, Unreal, Phaser, or Roblox only for the engine you choose, plus MCP server recommendations for AI-assisted development. - Validated Output Document: Generates an architecture document from a template with a decision summary table, project structure, implementation patterns, and a validation checklist to confirm AI-agent readiness. - Use Case: You are starting a 2D roguelike and need to decide between Godot and Unity, pick a save system, and define naming conventions so multiple AI agents implement consistently. Run the workflow to produce a complete, verified architecture document. ## Quick Start Ask the AI to design the game architecture for your project by saying "design architecture for my game" and follow the step-by-step workflow.

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 the workflow starting at step-01-init.md, which guides you through engine selection, system decisions, and implementation patterns. The output is an architecture document with a decision summary table, project structure, and consistency rules that AI agents can follow without ambiguity.

Which game engine should I choose: Unity, Unreal, or Godot?

The decision catalog maps requirements to engines: Unreal for high-fidelity 3D, Unity for cross-platform and mobile, Godot for open-source and 2D projects. The workflow loads an engine-specific knowledge fragment and verifies current versions via web search before finalizing the choice.

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, and lag compensation. Suggested stacks include dedicated servers, client-side prediction, and engine-native netcode options.

What MCP servers are recommended for game engines?

The engine-mcps.yaml catalog lists MCP servers per engine, such as MCP Unity and CoplayDev for Unity, unreal-mcp for Unreal, GoPeak for Godot, and the official Roblox Studio MCP. The workflow presents the top options and records whether you accept MCP setup in the architecture.

When is Godot the wrong choice for a game project?

Godot is a poor fit when AAA-quality 3D visuals are required, console launch is mandatory, or VR is the primary platform. Console export requires third-party porting companies under NDA, adding cost and timeline risk that the knowledge fragment flags during decision-making.