unity-adr

Document Unity architecture decisions with options, rationale, and consequences.

Updated Aug 23, 2026

Search Tags:#architecture #unity #documentation #adr #design-decision #tradeoff

Ready to run

npx skills add https://github.com/mandexonla/Top-Down-Template --skill unity-adr-mandexonla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/mandexonla/Top-Down-Template/tree/main/.codex/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/mandexonla/Top-Down-Template --skill unity-adr-mandexonla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and preserves architecture decision records for Unity projects so teams can compare options, document chosen approaches, and retain rationale for future revisits, reducing costly rework and ambiguity.

Core Features & Use Cases

Structured ADR output: Produces concise Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers.
Decision assistance: Helps evaluate tradeoffs for Unity-specific questions such as Coroutine vs UniTask, direct references vs event-driven communication, ScriptableObject config vs in-scene authoring, and asmdef organization.
Team alignment & documentation: Suitable for design reviews, pull requests, and repository ADR folders to keep choices discoverable and revisitable.

Quick Start

Create an ADR comparing Coroutine and UniTask and recommend the chosen approach with concise rationale and consequences.

Frequently Asked Questions about unity-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document architecture decisions for Unity projects?▼

To document Unity architecture decisions, generate structured records that capture the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers for team alignment.

What is the best way to compare Coroutine vs UniTask for my game?▼

Comparing Coroutine vs UniTask requires evaluating tradeoffs in asynchronous execution. Document the chosen approach with concise rationale, noting performance consequences and revisit triggers for future technical reviews.

How do I structure ScriptableObject configuration decisions during design reviews?▼

Structuring ScriptableObject configuration decisions during design reviews involves comparing in-scene authoring versus asset-based config, then documenting the selected approach with rationale and revisit triggers.

Can I use ADRs to organize asmdef dependencies in Unity?▼

You can use ADRs to organize asmdef dependencies by documenting the context, evaluating structural options, recording the chosen assembly organization, and defining revisit triggers for future architectural changes.

What should an architecture decision record include for runtime service placement?▼

An architecture decision record for runtime service placement should include the decision context, options considered, the chosen placement strategy, rationale, consequences, and revisit triggers to ensure team alignment.