Unity Architecture Advisor

Documentation only: no REST skills. Use before generating many gameplay scripts or when the user asks for a cleaner architecture.

When to use

• Planning code organization
• Splitting responsibilities
• Reducing coupling
• Choosing a refactor direction

Workflow

1. Identify scope: prototype, small game, or long-lived project.
2. Define the core loop and the minimum runtime systems needed.
3. Recommend the smallest architecture that fits the scope.
4. Separate: scene/bootstrap layer, gameplay/domain logic, data/config assets, view/presentation layer.
5. Call out what should stay simple now and what is worth abstracting.