unity-asmdef

Plan Unity assembly definition boundaries to create a shallow, directional dependency graph that isolates modules. This limits recompilation scope to changed assemblies, reducing overall compile times by avoiding unnecessary rebuilds of unaffected code.

Create separate Unity assembly definitions for editor-only and runtime code to enforce strict isolation. This prevents editor dependencies from leaking into runtime builds, keeping each layer maintainable and avoiding circular references between editor and runtime scripts.

Create a small, meaningful set of Unity assembly definitions representing cohesive modules rather than fragmenting into tiny assemblies. Over-fragmenting causes dependency sprawl and circular references, so group related functionality to balance compile speed with maintainability.

Outline practical migration steps to move an existing Unity codebase toward a cleaner asmdef layout with limited churn. Introduce assembly definitions gradually, defining directional dependencies and editor-runtime-test splits to control churn risk and avoid breaking existing references.

Fix circular references in Unity assembly definitions by designing a shallow, directional dependency graph that avoids shared dumping grounds. Restructure modules so dependencies flow in one direction, extracting shared code into isolated assemblies to break cyclic dependency chains.

Avoid Unity assembly definitions if your project is too small to benefit from module separation or if splitting would create unnecessary dependency sprawl. Without clear editor-runtime-test separation needs, asmdefs add structural overhead without meaningfully improving compile times.