What problem does it solve? Unity projects often grow into tangled MonoBehaviour scripts with hidden execution-order bugs and tight coupling. This Skill provides structured architectural guidance before you write structural code, helping you choose the smallest architecture that fits your project scope. ## Core Features & Use Cases - Scoped Architecture Planning: Recommends 3-7 modules with clear responsibilities based on whether your project is a prototype, small game, or long-lived product. - Execution Order & Guard Guidance: Explains Bootstrap entry-point patterns, DefaultExecutionOrder usage, and Update guard clauses to prevent null-data bugs. - Layered Separation Advice: Defines boundaries between scene/bootstrap, gameplay logic, data/config assets, and presentation layers, including when to use ScriptableObjects versus plain C# classes. - Use Case: Before building a new card battle system in Unity, ask for an architecture plan and receive module boundaries, a scene composition plan, communication rules, and a do-now/skip-now list. ## Quick Start Ask the assistant to plan the architecture for your Unity gameplay feature, describing your project scope and core game loop.
