What problem does it solve? When building Unity projects, teams repeatedly face architecture choices—Coroutine vs UniTask, direct references vs event-driven communication, one assembly vs multiple asmdefs—and the reasoning behind those choices is often lost, causing the same debates to resurface later. ## Core Features & Use Cases - Structured ADR Format: Produces a consistent record covering Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers. - Unity-Specific Scenarios: Covers common Unity tradeoffs such as ScriptableObject config vs in-scene authoring and MonoBehaviour vs pure C# services. - Use Case: When a developer asks whether to use UniTask or coroutines for async logic, the Skill compares both options, weighs tradeoffs, and locks in a documented decision with rationale that the team can revisit later. ## Quick Start Ask the agent to record an architecture decision comparing two Unity approaches, such as "help me decide between event-driven communication and direct references and document the decision."
