unity-adr

Create structured Architecture Decision Records for Unity projects with YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions in Unity projects can be revisited or require explicit justification; this ADR helps teams capture design tradeoffs in a clear, reusable format.

Core Features & Use Cases

  • Provides a structured template for Architecture Decision Records in Unity projects.
  • Captures options considered, rationale, consequences, and revisit triggers to guide future revisions.
  • Use Case: Decide between Coroutine-based patterns and UniTask, or between ScriptableObject configs and in-scene data, with a documented rationale.

Quick Start

Create an architecture decision record for the selected Unity design option using the ADR template.

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 and tradeoffs?

You can document Unity architecture decisions using a structured ADR template that captures decision context, options considered, the chosen option, rationale, and consequences for future revisits.

What is an Architecture Decision Record in Unity development?

An Architecture Decision Record in Unity is a structured document that captures design tradeoffs, available options, explicit justification, and revisit triggers to guide future architectural revisions.

How do I decide between UniTask and Coroutines with a documented rationale?

To decide between UniTask and Coroutines with documented rationale, use an ADR template to record both options, evaluate their tradeoffs, state the chosen option, and log the consequences.

Can I use this ADR template for ScriptableObject vs in-scene data decisions?

Yes, you can use this ADR template for ScriptableObject vs in-scene data decisions by recording the context, comparing options, capturing tradeoffs, and defining revisit triggers for the chosen config design.

Does the Unity ADR template require a specific metadata format?

The Unity ADR template requires a YAML frontmatter format that includes a name and description, alongside sections for decision context, options, chosen option, rationale, and consequences.