game-architect

Validate game architecture by running comprehensive checks that verify three-layer separation, enforce layer boundaries, detect import cycles, and confirm code organization standards are met. This ensures architectural drift hasn't occurred and the codebase meets release quality gates.

Code quality validation detects game logic in engine layers, rendering code in simulation layers, circular import dependencies, oversized files, and organizational drift. It validates that separation of concerns is maintained across sim, sim_gen, engine, and cmd layers.

Run architecture validation before version tagging, after major refactors, or on-demand when you need to verify codebase structure. It's a pre-release quality gate that confirms all files are in correct layers and no architectural issues block stable deployment.

Yes. Static analysis checks file sizes, directory organization, and absence of import cycles to validate code structure. Combined with layer boundary enforcement, it catches architectural violations without requiring code execution.

You need git, make, and go installed. The validation applies to codebases organized in layers (sim, sim_gen, engine, cmd) and is designed for projects following a three-layer architecture pattern.