What problem does it solve? Large Unity projects suffer from slow compile times and tangled code dependencies when everything lives in one default assembly. 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 - Justification Assessment: Evaluates whether your project size, domain count, and compile times actually warrant introducing asmdef files. - Architecture Proposal: Outputs proposed assemblies, allowed dependency direction, and an editor/runtime/test split plan. - Migration Guidance: Provides step-by-step migration steps plus risks and churn to avoid, such as circular dependencies or dumping-ground assemblies. - Use Case: Your Unity project's compile times have grown painful and editor scripts are mixed with runtime code. Ask for an asmdef plan and receive a directional dependency graph with a clean editor/runtime/test separation. ## Quick Start Ask the agent to review my Unity project structure and propose an asmdef layout that separates editor, runtime, and test code to speed up compilation.
