unity-adr
GitHub用于记录 Unity 架构决策（ADR），涵盖技术方案选型、库/模式对比及设计决策的来龙去脉。保持文档简洁，仅记录对代码生成或架构有实质影响的决策，包含决策背景、选项、选择理由及后果。
Trigger Scenarios
Install
npx skills add Besty0728/Unity-Skills --skill unity-adr -g -y
SKILL.md
Frontmatter
{
"name": "unity-adr",
"description": "Record Unity architecture decisions (ADR) with rationale"
}
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
MonoBehaviourvs 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.
Version History
-
5ee8388
Current 2026-08-17 04:09
Root SKILL.md 精简至 6.2KB，新增指南模式文档及 manual-* 建议模块；更新协议细节至参考文件；版本锚点更新至 2.6.0。
-
25d511e
2026-08-13 09:12
压缩了75个SKILL.md的描述至约5,191字符，并将路由说明移至Triggers部分。
- ec9f870 2026-07-05 14:39
