unity-script-roles

Assigning clear responsibilities to Unity scripts prevents overusing MonoBehaviour by categorizing each class as a bridge, ScriptableObject config, pure C# service, presenter, state node, or installer, outputting per-script justifications for the recommended role.

Use ScriptableObject for configuration and data in Unity gameplay systems, but avoid it for runtime-only state. A pure C# service handles runtime domain logic, ensuring clear separation between static config and dynamic runtime behavior.

The best way to plan Unity script architecture is to analyze your script list and output per-script recommendations detailing the recommended role, main responsibility, main dependencies, and a short justification to reduce coupling and prevent ambiguous class responsibilities.

Yes, you can use pure C# domain service classes for Unity gameplay logic instead of defaulting to MonoBehaviour. This prevents inappropriate MonoBehaviour usage and keeps runtime logic decoupled from the Unity component lifecycle.

Separating MonoBehaviour bridge classes from presenters or controllers in Unity clarifies class responsibilities, ensuring bridges only handle lifecycle integration while presenters manage application logic, thereby reducing coupling and runtime mistakes.

Refactoring Unity script roles helps prepare inputs for AI code generation by providing explicit class responsibilities, main dependencies, and structured role assignments like installer or state node, ensuring the AI understands the architectural context before generating code.