Record Unity architecture decisions and compare candidate design approaches.
npx skills add https://github.com/Rayzerrek/dotfiles --skill unity-adr-rayzerrek
Please help me install this Agent Skill. Skill: unity-adr Source: https://github.com/Rayzerrek/dotfiles/tree/main/.pi/agent/skills/unity-skills/skills/adr Command: npx skills add https://github.com/Rayzerrek/dotfiles --skill unity-adr-rayzerrek
This Skill helps you capture important Unity architecture decisions when several approaches are plausible and the choice may need to be revisited later. It turns an implicit debate into a clear, reusable record of what was decided and why.
Use this skill to compare the Unity options I am considering and draft a concise ADR with the decision, rationale, consequences, and revisit triggers.
High-intent search queries and answers about installing and using this skill.
You document Unity architecture decisions by recording context, options considered, chosen option, rationale, consequences, and revisit triggers in a concise ADR. This turns implicit debates over patterns like Coroutine vs UniTask into a clear, reusable record.
An architecture decision record (ADR) captures important architectural choices, comparing candidate approaches and documenting the chosen path with rationale and consequences. You need one for Unity scenarios like library selection, communication patterns, or assembly layout when choices may be revisited later.
Compare Unity design patterns by weighing tradeoffs between competing approaches and producing a concise ADR. The output includes context, options considered, chosen path, rationale, consequences, and revisit triggers for choices like event-driven communication versus direct reference.
Yes, you can use an ADR for Unity configuration strategies. It applies to choices like ScriptableObject config versus in-scene authoring, documenting the decision context, comparing options, and recording rationale, consequences, and revisit triggers for future reference.
A Unity ADR for assembly layout decisions should include context, options considered, chosen option, rationale, consequences, and revisit triggers. This structure ensures decisions like one assembly versus multiple asmdef are clearly documented and easily revisitable.
jabrenaGenerate Architecture Decision Records for Java projects through interactive conversation.
dyCuong03Capture Unity architecture decisions in a structured ADR format.
anavvanzinConvert Unity projects into modular, data-driven ScriptableObject architectures.
groupzer0Standardize architecture patterns, ADRs, and anti-pattern detection for design reviews.
