skills.rest
du-qwq
du-qwqCOMMUNITY
Explore all skills by this author →
GitHub

unity-adr

Documents Unity architecture decisions with options, tradeoffs, and rationale.

Updated Jun 21, 2026
Search Tags:#game development#unity#documentation#adr#technical selection#architecture decision#tradeoff analysis
One-click install
npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-adr-du-qwq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications/tree/main/.agents/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-adr-du-qwq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity projects accumulate technical choices—Coroutine vs UniTask, event-driven vs direct references, single vs multiple asmdefs—that get revisited and re-debated when the original reasoning is lost. This Skill captures those decisions in a consistent Architecture Decision Record format so the rationale stays with the codebase. ## Core Features & Use Cases - Structured ADR Format: Records Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers. - Tradeoff Comparison: Compares multiple plausible technical approaches and locks in a chosen one with explicit reasoning. - Use Case: When deciding between ScriptableObject config and in-scene authoring, use this Skill to weigh both options, document the winner, and note the conditions under which the decision should be revisited. ## Quick Start Ask the assistant to record an ADR comparing Coroutine and UniTask for your async logic and document which one the project should use.

Frequently Asked Questions about unity-adr

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

FAQPage Schema
How do I document an architecture decision in a Unity project?▼

Write an Architecture Decision Record covering the decision, context, options considered, chosen option, why it won, consequences, and revisit triggers. Keep it short and only record decisions that materially affect code generation or architecture direction.

Coroutine vs UniTask for Unity async code?▼

This is a classic Unity tradeoff worth recording as an ADR. Compare both options against your project's context, document which one wins and why, and note consequences and conditions that would trigger revisiting the choice.

When should I write an ADR instead of just deciding?▼

Write an ADR when multiple plausible options exist or when the choice may be revisited later. Skip it for trivial decisions that do not materially affect architecture direction or code generation.

Does this skill generate or modify Unity code?▼

No, it is documentation-only. It produces a structured decision record and does not execute scripts, call APIs, or change project files, so it loads freely under any operating mode.

What sections should a good ADR include?▼

A good ADR includes Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers. This structure keeps rationale explicit and makes future re-evaluation straightforward.

Related Skills

Explore More Software Engineering Skills→
RayzerrekRayzerrek

unity-adr

Record Unity architecture decisions and compare candidate design approaches.

Community
Intermediate
mandexonlamandexonla

unity-adr

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

Community
Intermediate
nlelouchenlelouche
71

unified-style-guide

Generate a standardized .editorconfig file for Unity C# projects.

Community
Intermediate
PMK95PMK95

editor-selection-set

Sets the Unity Editor selection to specified objects via ObjectRef instance IDs.

Community
Basic