What problem does it solve? Architecture choices in Unity projects are often revisited months later with no record of why a particular approach was chosen, leading to repeated debates and inconsistent code. This Skill captures those decisions in a structured Architecture Decision Record (ADR) format so the reasoning stays with the project. ## Core Features & Use Cases - Structured ADR Output: Produces a consistent record covering Decision, Context, Options considered, Chosen option, Rationale, Consequences, and Revisit triggers. - Unity-Specific Scenarios: Tailored to common Unity trade-offs such as Coroutine vs UniTask, direct references vs event-driven communication, ScriptableObject config vs in-scene authoring, and MonoBehaviour vs pure C# services. - Use Case: When deciding between a single assembly and multiple asmdef files for a growing Unity codebase, use this Skill to document the options weighed, the final choice, and the conditions under which the decision should be revisited. ## Quick Start Ask the assistant to record an ADR for your Unity decision, for example: document why we chose UniTask over Coroutines for async logic in this project.
