ScriptableObject Architecture

Generate SO patterns for data, events, and runtime collections.

Before You Start

1. Read docs/ProjectConfig.yaml for:
   • architecture_pattern — "so-first" (default, this skill is primary) or "di-first" (SOs still hold data, but events become Commands — see uw-dependency-injection).
   • mcp.unity_mcp — if true, call refresh_unity after creating files.
2. Read docs/TDD_Template.md for data architecture decisions.
3. Read docs/NAMING_CONVENTIONS.md for SO file naming (PascalCase: SwordData.asset).
4. Ensure the feature has an .asmdef — create with uw-unity-feature-scaffold if needed.

Three Patterns

1. Data Container

Store game-tunable values in a ScriptableObject. Designers edit them in the Inspector without touching code.