unity-adr

Record architecture decisions for Unity projects with structured ADR templates.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Yuan-Zzzz/FrogRE --skill unity-adr-yuan-zzzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/Yuan-Zzzz/FrogRE/tree/main/.codex/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/Yuan-Zzzz/FrogRE --skill unity-adr-yuan-zzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams face multiple plausible implementation approaches in Unity, decisions can be forgotten, argued, or re-made inconsistently; this Skill helps capture concise architecture decision records to preserve rationale, trade-offs, and revisit triggers for future maintainers.

Core Features & Use Cases

  • Structured ADR template: Produces Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers.
  • Options comparison: Helps compare trade-offs like Coroutine vs UniTask, direct references vs event-driven communication, ScriptableObject config vs in-scene authoring, and asmdef strategies.
  • Team-ready output: Keeps ADRs short and focused so they can be included in project documentation without blocking development.

Quick Start

Create an ADR that compares Coroutine and UniTask approaches and recommends one with a short explanation of trade-offs 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 Unity architecture decisions for trade-offs like Coroutine vs UniTask?

To document Unity architecture decisions, you create concise ADRs capturing context, options considered, chosen option, rationale, consequences, and revisit triggers for trade-offs like Coroutine vs UniTask. This Skill produces that structured ADR output directly.

What is an Architecture Decision Record and why do I need one for my Unity project?

An Architecture Decision Record (ADR) is a concise document that captures the rationale, trade-offs, and consequences of a software design choice. You need ADRs for Unity projects so that decisions are not forgotten, argued, or re-made inconsistently by future team maintainers.

How do I compare ScriptableObject configuration versus in-scene authoring in Unity?

You compare ScriptableObject configuration versus in-scene authoring by structuring the evaluation as an ADR that defines the context, lists both options, and records the chosen option, why it won, and consequences. This Skill applies that template to Unity-specific trade-offs.

Can I use this to record assembly definition strategies for Unity codebases?

Yes, you can use this to record assembly definition strategies for Unity codebases. The Skill evaluates trade-offs and produces concise ADRs covering decision, context, options, and consequences suitable for any Unity architecture evaluation, including asmdef strategies.

What is the best way to keep Unity architecture documentation concise enough for team use?

The best way to keep Unity architecture documentation concise is to use a structured ADR template that focuses strictly on decision, context, options, and consequences. This Skill ensures output remains short and team-ready without blocking development.