unity-scriptdesign

Review Unity scripts by checking single responsibility, correct choice between MonoBehaviour, ScriptableObject, and plain C# class, explicit dependencies, and cleanup of subscriptions and async work. This skill provides a checklist covering all of these plus naming and testability.

Use ScriptableObject for authoring-time data decided by designers before Play, such as weapon damage or level music, so balance values stay immutable at runtime and hot-swappable. Use MonoBehaviour for scene-attached behaviour and plain C# classes for testable core logic.

Reduce coupling by making dependencies explicit through cached references assigned in Awake, constructor arguments, interfaces, or events instead of hidden globals and deep scene lookups. Avoid repeated Find calls and per-frame GetComponent lookups.

This happens when a field has two owners, such as a public float edited both in the Inspector and by a power-up script. Separate state into authoring-time, composition-time, and runtime-mutable lifecycles so each value has exactly one owner.

Look for unnecessary Update methods, repeated Find or GetComponent calls, avoidable allocations, and reflection in hot paths. Cache component references once at composition time and only flag real hotspots rather than theoretical micro-optimizations.