unity-asmdef

Advises on Unity assembly definition layout, dependency direction, and compile boundaries.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill unity-asmdef-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-asmdef
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/unity-skills/skills/asmdef
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill unity-asmdef-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about unity-asmdef

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure asmdef files in a large Unity project?

Prefer a few meaningful assemblies over many tiny ones, split editor code from runtime first, and keep the dependency graph directional and shallow. Define clear allowed dependency directions between assemblies before migrating code.

When should I use assembly definitions in Unity?

Assembly definitions are worth it when the project has multiple domains or systems, editor and runtime code are mixed, compile times become noticeable, or tests need clean isolation. Avoid them for tiny prototypes.

How do I speed up Unity compile times with asmdef?

Splitting code into assemblies with asmdef files lets Unity recompile only changed assemblies instead of the entire project. Separate editor and runtime code first, then isolate stable systems from frequently changing ones.

What are the risks of using too many asmdef files?

Excessive fragmentation creates maintenance churn, forces everything through a shared dumping-ground assembly, and can introduce circular dependencies. Keep assemblies few, meaningful, and directionally dependent.

How do I split editor and runtime code in Unity?

Place editor scripts in separate assemblies that reference the runtime assembly but are never referenced back. This keeps runtime builds clean and prevents editor-only APIs from leaking into shipped code.