component-design

Structure Unity MonoBehaviour scripts by applying a decision framework to split monolithic components, ensuring single responsibility for maintainable architecture. This involves dividing component responsibilities and ordering lifecycle methods.

The best way to split a monolithic Unity MonoBehaviour is using a decision template that evaluates responsibilities, determining when to divide scripts to reduce complexity and improve maintainability across the architecture.

Handle Unity component communication by applying recommended inter-component communication patterns provided by the framework, ensuring focused scripts interact predictably without reintroducing monolithic dependencies.

Unity MonoBehaviour lifecycle ordering best practices involve standardizing the sequence of lifecycle methods to ensure predictable execution and maintainable architecture across divided components.

Refactor a Unity MonoBehaviour into multiple components when the script violates single responsibility, using the decision framework to determine exactly when to split, select communication patterns, and order lifecycle methods.