# Unity Asmdef

> Assembly definition advisor for Unity projects. Use when users want module boundaries, faster compilation, cleaner dependencies, or editor/runtime/test separation. Triggers: asmdef, assembly definition, module boundary, compile time, slow compilation, dependency graph, 程序集, 模块边界, 编译慢, 依赖管理, asmdef怎么配.

- Skill: `noah-zll/unity-asmdef` (Agent Skill)
- Install (CLI): `npx skillmds@latest add noah-zll/unity-asmdef`
- Raw SKILL.md: https://api.skillmd.com/api/skills/noah-zll/unity-asmdef/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: noah-zll (https://skillmd.com/u/noah-zll)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/noah-zll/unity-asmdef

---


# Unity asmdef Advisor

Use this skill when the project is large enough that compile boundaries and dependency direction matter.

## Recommend Only When Worth It

`asmdef` is usually worth discussing when:

- the project has multiple domains/systems
- editor code and runtime code are mixed
- compile times are becoming noticeable
- tests should be isolated cleanly

## Output Format

- Whether `asmdef` is justified now
- Proposed assemblies
- Allowed dependency direction
- Editor/runtime/test split
- Migration steps
- Risks or churn to avoid

## Default Guidance

- Prefer a few meaningful assemblies over many tiny ones.
- Split editor code from runtime first.
- Keep the dependency graph directional and shallow.

## Guardrails

**Mode**: Both (Semi-Auto + Full-Auto) — advisory only, no REST skills

- Do not introduce `asmdef` fragmentation for a tiny prototype.
- Do not create circular dependencies or force everything through a shared dumping-ground assembly.