unity-foundation

To enforce Unity assembly boundaries, separate editor and runtime code into dedicated assemblies and establish test assemblies so dependencies flow Tests to Runtime to Editor, keeping compilation fast and preventing integration drift in hybrid ECS and MonoBehaviour projects.

Managing scene lifecycle entry and exit semantics requires defining explicit bootstrap ordering and cleanup expectations for ECS and MonoBehaviour components. This ensures consistent scene entry and disposal behavior and reduces runtime errors during transitions in hybrid architectures.

Compilation friction and navigation confusion in large Unity repos usually stems from inconsistent assembly definitions and unclear code boundaries. Mapping asmdef boundaries and checking workspace guidance files enforces separation to reduce this drift.

Structure MonoBehaviour wrappers as thin components that apply guard clauses while keeping ECS systems clean. This Unity-specific code quality approach reduces maintenance cost and runtime errors by ensuring wrappers handle bootstrap without polluting ECS logic.

Scene lifecycle contracts apply to ECS plus MonoBehaviour hybrid projects where scenes need clear entry and exit semantics. Treat this guidance as secondary to ECS skills and use Unity-safe practices for MonoBehaviour wrappers and debug logging.

You should maintain asmdef separation for editor and runtime code whenever your Unity project has distinct editor tooling and runtime logic. Avoid skipping this separation if you want fast compilation and clean dependency flow from Tests to Runtime to Editor.