unity-architecture

1> **Before calling any skill in this module:** if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via `GET /skills/recommend?includeSchema=true`) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.
2 
3## Triggers
4- Planning code organization
5- Splitting responsibilities
6- Reducing coupling
7- Choosing refactor direction
8- 规划代码结构、划分职责、降低耦合、确定重构方向
9 
10# Unity Architecture Advisor
11 
12Use this before generating lots of gameplay scripts or when the user asks for a cleaner architecture.
13 
14## Workflow
15 
161. Identify scope: prototype, small game, or long-lived project.
172. Define the core loop and the minimum runtime systems needed.
183. Recommend the smallest architecture that fits the scope.
194. Separate:
20   - scene/bootstrap layer
21   - gameplay/domain logic
22   - data/config assets
23   - view/presentation layer
245. Call out what should stay simple now vs what is worth abstracting.
25 
26## Output Format
27 
28When using this skill, structure the advice as:
29 
30- Project tier: prototype / small-game / long-lived
31- Recommended modules: 3-7 modules with one-line responsibilities
32- Scene/bootstrap plan: where composition and initialization happen
33- Data ownership: what belongs in scene objects, ScriptableObjects, or pure C# classes
34- Communication rules: direct refs, interfaces, events, or commands
35- Performance risks: only the hot paths that matter
36…