skills.rest
dyCuong03
dyCuong03COMMUNITY
Explore all skills by this author →
GitHub

unity-adr

Capture Unity architecture decisions in a structured ADR format.

6|Updated Apr 2, 2026
Search Tags:#unity#adr#design documentation#systems design#architecture decision record#tradeoffs
One-click install
npx skills add https://github.com/dyCuong03/unity-agent-team --skill unity-adr-dycuong03
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill unity-adr-dycuong03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you capture and communicate Unity architecture decisions so future work has clear reasoning and a consistent direction.

Core Features & Use Cases

  • Decision documentation: Produces a structured ADR covering the decision, context, options, and rationale.
  • Tradeoff clarity: Captures alternatives and why the chosen approach won, including pros and cons implicitly through options and reasons.
  • Long-term maintainability: Records consequences and explicit revisit triggers to handle evolving requirements over time.
  • Use cases: Choose between architectural patterns (e.g., coroutine vs UniTask), decide communication style (direct references vs event-driven), and set boundaries for assemblies and systems (one assembly vs multiple asmdef, MonoBehaviour logic vs pure C# services).

Quick Start

Write: “Create an ADR for choosing between UniTask and coroutines for my Unity DOTS project, including options, chosen approach, rationale, consequences, and when to revisit.”

Frequently Asked Questions about unity-adr

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

FAQPage Schema
How do I document Unity architecture decisions for evolving project tradeoffs?▼

You document Unity architecture decisions by creating an Architecture Decision Record capturing the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers for evolving tradeoffs.

What is an ADR in Unity systems design and when do I need one?▼

An ADR in Unity systems design is a structured format recording architectural choices like framework selection or module structuring, needed when managing evolving design tradeoffs and ensuring long-term maintainability.

How do I create an ADR for choosing between UniTask and coroutines in Unity?▼

To create an ADR for choosing between UniTask and coroutines, prompt the system with your decision context, and it outputs a structured record covering options, chosen approach, rationale, consequences, and revisit triggers.

Can I use an ADR to decide Unity assembly structuring and module boundaries?▼

Yes, you can use an ADR to decide Unity assembly structuring by documenting whether to use one assembly versus multiple asmdef files or MonoBehaviour logic versus pure C# services as structured options with rationale.

What is the best way to capture rationale for Unity communication style choices like event-driven versus direct references?▼

The best way to capture rationale for Unity communication style choices is an ADR format explicitly recording alternatives considered, why the chosen approach won, and the consequences of choosing event-driven or direct references.

Related Skills

Explore More Software Engineering Skills→
jinlulijinluli

unity-asmdef

Advise on creating and managing assembly definitions in Unity projects.

Community
Intermediate
ForgePlanForgePlan
3

decay-watch

Monitor Revisit Triggers in active ADR artifacts for evidence decay.

Official
Intermediate
RayzerrekRayzerrek

unity-adr

Record Unity architecture decisions and compare candidate design approaches.

Community
Intermediate
alsmadi99alsmadi99

architecture-designer

Design high-level software architectures and document decisions with Architecture Decision Records.

Community
Advanced