unity-adr

Record Unity architecture decisions with structured ADR templates.

8|1|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/Zzulin/unity-project01 --skill unity-adr-zzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/Zzulin/unity-project01/tree/main/URP1/Plugins/Unity-Skills-main/SkillsForUnity/unity-skills~/skills/adr
Command: npx skills add https://github.com/Zzulin/unity-project01 --skill unity-adr-zzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams capture, compare, and document architectural decisions in Unity projects so choices and tradeoffs are preserved and revisited with context.

Core Features & Use Cases

  • Structured ADR template: Produces concise entries including Decision, Context, Options considered, Chosen option, Rationale, Consequences, and Revisit triggers.
  • Decision guidance: Advises on tradeoffs for common Unity patterns such as Coroutine vs UniTask, direct references vs event-driven communication, ScriptableObject configs vs in-scene authoring, and assembly boundaries.
  • Guardrails: Encourages short, impactful ADRs and records only decisions that materially affect architecture or code generation.
  • Use Case: When choosing between single assembly or multiple asmdef files, use this Skill to compare options and record the final choice and its consequences.

Quick Start

Create an ADR comparing Coroutine and UniTask for asynchronous workflows in a Unity project and recommend a choice with pros, cons, consequences, and revisit triggers.

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 a Unity project?

You document Unity architecture decisions by creating concise Architecture Decision Records that capture the context, options considered, chosen option, rationale, consequences, and revisit triggers. This Skill generates structured ADRs to preserve tradeoff context for future audits.

What is the best way to compare Coroutine and UniTask for asynchronous workflows in Unity?

Comparing Coroutine and UniTask for Unity asynchronous workflows requires evaluating tradeoffs and documenting the chosen option with rationale and consequences. This Skill produces ADRs that record these comparisons, ensuring future teams understand why a specific async pattern was selected.

When should I create an architecture decision record for Unity assembly boundaries?

You should create an architecture decision record for Unity assembly boundaries when the choice between single or multiple asmdef files materially affects project architecture. This Skill records decisions that impact code generation guidance and establishes revisit triggers for future audits.

How do I record tradeoffs between ScriptableObject configs and in-scene authoring in Unity?

To record tradeoffs between ScriptableObject configs and in-scene authoring in Unity, you formalize the decision context, options, and consequences into an ADR. This Skill provides a structured template to ensure configuration strategies are preserved and revisitable.

What should a Unity architecture decision record include to support future audits?

A Unity architecture decision record should include the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers. This Skill enforces these fields to support future audits and provide code generation guidance.