What problem does it solve? Designing large-scale Godot 4.x games often leads to tight coupling, signal spaghetti, and performance bottlenecks when developers lack clear rules for data ownership, signal topology, and scene boundaries. ## Core Features & Use Cases - Architecture Decision Framework: Provides a three-question ownership model, a layered signal topology (presentation, logic, data, infrastructure), and a decision matrix mapping project types (RPG, open world, multiplayer, mobile) to architecture strategies. - Performance Budgets & Gotchas: Supplies concrete mobile/desktop budgets for draw calls, physics bodies, and script time, plus documented Godot 4.x pitfalls like shared @export Resources and signal syntax changes. - Use Case: When building a complex RPG with combat and inventory systems, use this Skill to choose a component-driven architecture, define scoped signal buses, and apply expert patterns like state machine transition guards and async level loading. ## Quick Start Ask the AI to design the architecture for a Godot 4.x RPG with a combat system, defining data ownership, signal flow, and scene boundaries.
