Dependency Injection (Reflex)

DI-first architecture for complex Unity projects. Only applies when ProjectConfig.yaml -> architecture_pattern: di-first. For simpler projects, use uw-scriptable-object-arch (SO-first) instead.

Before You Start

1. Read docs/ProjectConfig.yaml for:
   • architecture_pattern — must be "di-first" for this skill to apply.
   • di_framework — should be "reflex" (the default and recommended framework).
   • mcp.unity_mcp — if true, call refresh_unity after creating files.
2. Read docs/CODING_STANDARDS.md for async patterns (Awaitable + CancellationToken), access modifiers (internal for cross-class helpers within an asmdef), and class structure.
3. Read docs/NAMING_CONVENTIONS.md for file/class naming.
4. Ensure each feature module has its own .asmdef — create with uw-unity-feature-scaffold. Installers, Controllers, Services all live inside feature asmdefs.

When to Use DI vs SO-First