What problem does it solve?
Game development teams often begin implementation without a unified technical blueprint, leading to misalignment between game design documents and code, inconsistent system boundaries, and costly late-stage fixes from unaddressed engine compatibility gaps.
Core Features & Use Cases
- Guided End-to-End Architecture Authoring: Phase-by-phase workflow that translates all approved game design documents (GDDs) into a complete master architecture document covering system layers, module ownership, data flows, and API boundaries.
- Engine-Version Validation: Automatically flags knowledge gaps for post-cutoff engine changes and validates all architectural decisions against the pinned target engine version to avoid compatibility issues.
- ADR Gap Analysis: Audits existing architecture decision records (ADRs) for completeness, traceability to game requirements, and engine compatibility, producing a prioritized list of missing ADRs required before coding starts.
Use Case: A game studio preparing for pre-production can use this skill to produce an approved, engine-validated architecture document that gives all engineering teams a single source of truth for system design, ensuring all gameplay requirements are technically supported.
Quick Start
Use the create-architecture skill to generate a full master architecture blueprint for your game project, aligned with your approved GDDs and target engine version.