unity-game-architecture

What problem does it solve?

This Skill addresses common Unity architectural pitfalls by providing decision patterns for structuring game systems, managing dependencies, and facilitating communication between different parts of your game.

Core Features & Use Cases

• Service Access Patterns: Choose between Singleton, Service Locator, and Dependency Injection (DI) based on project needs.
• Class Design: Guidance on when to use MonoBehaviour versus plain C# classes.
• Communication: Strategies for event handling, including C# events, ScriptableObject channels, and static event buses.
• Use Case: You're starting a new Unity project and need to decide how your core systems (like audio, input, and save managers) will interact. This Skill helps you select the most appropriate pattern (e.g., Service Locator for testability) and provides scaffold code.

Quick Start

Use the unity-game-architecture skill to understand the trade-offs between Service Locator and Singleton patterns for global service access.