What problem does it solve? Unity projects often accumulate tangled MonoBehaviour scripts, hidden execution-order dependencies, and over-engineered frameworks. This Skill provides structured architecture guidance so gameplay code stays decoupled, testable, and appropriately sized for the project's scope. ## Core Features & Use Cases - Scoped Architecture Recommendations: Classifies the project as prototype, small game, or long-lived, then recommends 3-7 modules with clear responsibilities. - Layering and Data Ownership Guidance: Separates scene/bootstrap, gameplay logic, data/config assets, and presentation, and clarifies when to use MonoBehaviours, plain C# classes, or ScriptableObjects. - Execution Order and Guard Patterns: Explains explicit bootstrap initialization, DefaultExecutionOrder usage, and Update guard clauses to prevent null-data bugs. - Use Case: Before generating a batch of gameplay scripts for a new Unity game, ask for an architecture plan to define module boundaries, communication rules, and what to keep simple versus abstract. ## Quick Start Ask the assistant to use the unity-architecture skill to propose a module structure and bootstrap plan for your Unity game before writing gameplay scripts.
