mcpField
U
unity-adr

unity-adr

github.com/besty0728Development1.9k79 installsUpdated today
Repository

About unity-adr

unity-adr is a documentation skill for recording Unity architecture decisions, aimed at developers weighing plausible options or preserving rationale for later review. Its structured format captures context, alternatives, rationale, consequences, and revisit triggers.

Key features

  1. 01Record decisions and their context
  2. 02List and compare alternatives
  3. 03Explain the chosen option and rationale
  4. 04Capture consequences and revisit triggers
  5. 05Document decisions without executing REST skills

Use cases

  1. 01Compare Coroutine and UniTask
  2. 02Evaluate event-driven communication versus direct references
  3. 03Record a ScriptableObject configuration choice
  4. 04Decide how to split assemblies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/besty0728/unity-skills --skill unity-adr

After installing, type/unity-adrin Claude Code to confirm it loaded.

Details

From the project README

Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.

Triggers

  • Choosing between technical approaches
  • Comparing libraries or patterns
  • Documenting design rationale
  • 技术方案选型、库/模式对比、记录设计决策来龙去脉

Unity ADR

Use this when architecture choices may be revisited later or when multiple plausible options exist.

Output Format

  • Decision
  • Context
  • Options considered
  • Chosen option
  • Why this option won
  • Consequences
  • Revisit triggers

Example Use Cases

  • Coroutine vs UniTask
  • Direct reference vs event-driven communication
  • ScriptableObject config vs in-scene authoring
  • One assembly vs multiple asmdef
  • Runtime logic in MonoBehaviour vs pure C# service

Guardrails

Mode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).

  • Keep ADRs short.
  • Record only decisions that materially affect code generation or architecture direction.

Comments

Markdown supported