skills.rest
pcone-mm
pcone-mmCOMMUNITY
Explore all skills by this author →
GitHub

unity-adr

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

2|Updated May 18, 2026
Search Tags:#game development#unity#documentation#adr#technical selection#architecture decision#tradeoffs
One-click install
npx skills add https://github.com/pcone-mm/NewFPG --skill unity-adr-pcone-mm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/pcone-mm/NewFPG/tree/main/.agents/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/pcone-mm/NewFPG --skill unity-adr-pcone-mm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building Unity projects, teams repeatedly face technical choices—Coroutine vs UniTask, direct references vs event-driven communication, one assembly vs multiple asmdefs—without a record of why a decision was made. This Skill captures those architecture decisions in a consistent ADR format so the reasoning survives long after the choice is made. ## Core Features & Use Cases - Structured ADR Output: Produces a decision record with Decision, Context, Options considered, Chosen option, Why this option won, Consequences, and Revisit triggers. - Unity-Specific Scenarios: Covers common Unity dilemmas such as ScriptableObject config vs in-scene authoring and MonoBehaviour vs pure C# services. - Use Case: You are debating whether to use UniTask or Coroutines for async logic in a Unity project. Ask for an ADR and receive a concise record comparing both options, the chosen approach, its tradeoffs, and conditions that would trigger revisiting the decision. ## Quick Start Ask the assistant to record an ADR comparing Coroutine and UniTask for your Unity project's async logic.

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

Use an Architecture Decision Record (ADR) format that captures the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers. This Skill generates that structure for Unity-specific choices like async patterns or assembly organization.

Coroutine vs UniTask for Unity async code?▼

The Skill helps you weigh Coroutine against UniTask by documenting tradeoffs for your specific context rather than prescribing one answer. The resulting ADR records which option won, why, and what conditions would trigger revisiting the choice.

When should I write an ADR for a Unity decision?▼

Write an ADR when multiple plausible options exist or when a choice may be revisited later, such as ScriptableObject config vs in-scene authoring. Only record decisions that materially affect code generation or architecture direction, and keep them short.

Does this Skill generate or modify Unity code?▼

No, it is documentation-only and produces no code changes. It loads freely under any operating mode and focuses solely on recording the reasoning behind architecture decisions.

What are the limitations of ADR documentation?▼

ADRs only capture decisions at a point in time and can become stale if not revisited. This Skill mitigates that by including revisit triggers, but teams must still act on those triggers when conditions change.

Related Skills

Explore More Software Engineering Skills→
petrSimonidesXartpetrSimonidesXart

approach-evaluation

Evaluate technical approaches against project constraints with documented evidence.

Community
Advanced
krl76krl76

unity-adr

Generate structured Architecture Decision Records for Unity projects.

Community
Intermediate
rsmdtrsmdt
381

pattern-recognition

Identify codebase patterns to enforce naming, architecture, and testing conventions.

Community
Advanced
zhoulingxiao1216zhoulingxiao1216

spike

Build throwaway prototype experiments to validate technical feasibility before committing to a real build.

Community
Intermediate