domains / families / software-engineering / architecture

architecture

combined

Advise on Unity gameplay and system architecture Architecture design skill with ADR records, system design checklists, scalability assessment, and architecture patterns

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies cover different scopes and workflows. The first is a Unity-specific gameplay architecture advisor with concrete C#/MonoBehaviour execution-order and guard-clause rules. The second is a general system-design skill focused on ADRs, checklists, and patterns. The third is a general decision framework that references external files for context discovery, trade-offs, and pattern selection. No single copy is the procedure the others reproduce; each contains material steps or constraints the others lack.