unity-game-architecture

Structure your Unity game architecture using component composition to break down God MonoBehaviours. This Skill provides decision patterns and scaffold code for splitting monolithic scripts into manageable, focused systems to improve project maintainability.

The best way to manage dependencies depends on project needs; this Skill helps you choose between Singleton, Service Locator, and Dependency Injection. It provides scaffold code and trade-off analysis to ensure testable inter-system communication.

Handle communication between Unity game systems using event channels, C# events, or static event buses instead of excessive singletons. This Skill offers strategies to decouple system interactions and prevent anti-patterns.

Use plain C# classes versus MonoBehaviour based on whether the system requires Unity's lifecycle hooks or scene presence. This Skill provides decision patterns for class design to ensure your architecture remains robust and performant.

Yes, this Unity architecture guidance fully supports Unity 6.3 LTS development. It provides scaffold code and architectural decision patterns specifically tailored for structuring robust game systems within the Unity 6.3 LTS environment.

Use a Service Locator pattern for global service access in Unity to improve testability and reduce tight coupling compared to traditional Singletons. This Skill explains the trade-offs and provides scaffold code to implement it effectively.