unity-adr

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- Choosing between technical approaches
5- Comparing libraries or patterns
6- Documenting design rationale
7- 技术方案选型、库/模式对比、记录设计决策来龙去脉
8 
9# Unity ADR
10 
11Use this when architecture choices may be revisited later or when multiple plausible options exist.
12 
13## Output Format
14 
15- Decision
16- Context
17- Options considered
18- Chosen option
19- Why this option won
20- Consequences
21- Revisit triggers
22 
23## Example Use Cases
24 
25- Coroutine vs UniTask
26- Direct reference vs event-driven communication
27- ScriptableObject config vs in-scene authoring
28- One assembly vs multiple `asmdef`
29- Runtime logic in `MonoBehaviour` vs pure C# service
30 
31## Guardrails
32 
33> **Mode**: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).
34 
35- Keep ADRs short.
36- Record only decisions that materially affect code generation or architecture direction.