What problem does it solve? Large Unity projects suffer from slow compile times, tangled assembly dependencies, and mixed editor/runtime code. This Skill helps you decide whether assembly definitions (asmdef) are justified and how to structure them without creating fragmentation or circular dependencies. ## Core Features & Use Cases - asmdef Justification Assessment: Evaluates whether your project is large enough to benefit from assembly definitions based on domains, compile times, and test isolation needs. - Dependency Architecture Planning: Proposes assemblies with allowed dependency direction, keeping the graph directional and shallow. - Editor/Runtime/Test Splitting: Guides separation of editor code from runtime code and clean test isolation. - Use Case: Your Unity project has grown to multiple gameplay systems with noticeable compile times. Use this Skill to get a proposed assembly layout, migration steps, and risks to avoid before restructuring. ## Quick Start Ask the assistant to review my Unity project structure and propose an asmdef layout that splits editor, runtime, and test code with clear dependency direction.