mcpField
U
unity-assembly-management

unity-assembly-management

github.com/muharremtozanDevelopment1756 installsUpdated 22w ago
Repository

About unity-assembly-management

unity-assembly-management is a skill for structuring Unity projects with Assembly Definitions. It supports two dependency configuration approaches and provides scaffolding and validation for modular project boundaries.

Key features

  1. 01Support explicit GUID and version-based setup
  2. 02Support auto-referenced modules
  3. 03Enforce Runtime and Editor boundaries
  4. 04Scaffold Runtime, Editor, and Tests assemblies
  5. 05Validate architecture boundaries

Use cases

  1. 01Create a module with Runtime, Editor, and Tests assemblies
  2. 02Set up explicit assembly dependencies
  3. 03Check a Unity project for boundary violations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/muharremtozan/unity-agent-skills --skill unity-assembly-management

After installing, type/unity-assembly-managementin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/code/
AsmdefScaffolder.cs.txt
AsmdefTemplate.json.txt
AsmdefValidator.cs.txt
references/
guide.md

Details

From the project README

Unity Assembly Management

Manage project boundaries using Assembly Definitions (.asmdef) for faster compile times and modular architecture. Based on the patterns by Adam Myhre.

Core Features

  • Hybrid Approach: Supports both "Pro Path" (Explicit GUIDs, Version Defines) and "Light Path" (Auto-referenced modules).
  • Rule Enforcement: Enforces "Runtime never depends on Editor" and inward dependency flows.
  • Scaffolding: Automated creation of Runtime/Editor/Tests assembly splits.

Core Files

  • AsmdefTemplate.json.txt: Flexible template for various assembly configurations.
  • AsmdefScaffolder.cs.txt: Editor utility to generate standard module structures.
  • AsmdefValidator.cs.txt: Script to verify architectural boundaries.

Usage

  1. Use AsmdefScaffolder to create a new module partition.
  2. Define dependencies explicitly in the Inspector using GUIDs.
  3. Validate regularly to ensure no architectural drift has occurred.

Comments

Markdown supported