Skip to content
Skills Library
Programming · Building & coding

unity-editor-tooling

/unity-editor-tooling

Unity Editor scripting — custom Inspectors, PropertyDrawers, EditorWindow, MenuItems, asset post-processors, Editor Coroutines, automated builds via `-batchmode -executeMethod`. USE WHEN: building tools for designers, custom Inspector UI, gizmos, scene validators, asset import hooks, editor menu commands, headless CI builds. DO NOT USE FOR: runtime UI (use `unity-input-ui`); test runner (use `unity-testing`).

Licence
MIT
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Unity Editor scripting — custom Inspectors, PropertyDrawers, EditorWindow, MenuItems, asset post-processors, Editor Coroutines, automated builds via `-batchmode -executeMethod`. USE WHEN: building tools for designers, custom Inspector UI, gizmos, scene validators, asset import hooks, editor menu commands, headless CI builds. DO NOT USE FOR: runtime UI (use `unity-input-ui`); test runner (use `unity-testing`).

Original author description

Unity Editor scripting — custom Inspectors, PropertyDrawers, EditorWindow, MenuItems, asset post-processors, Editor Coroutines, automated builds via `-batchmode -executeMethod`. USE WHEN: building tools for designers, custom Inspector UI, gizmos, scene validators, asset import hooks, editor menu commands, headless CI builds. DO NOT USE FOR: runtime UI (use `unity-input-ui`); test runner (use `unity-testing`).

How it works

  1. Asmdef layout for editor code
  2. Custom Inspector
  3. PropertyDrawer
  4. EditorWindow
  5. Asset post-processor
  6. Headless builds (-batchmode)
  7. Anti-patterns
  8. Production checklist
Original SKILL.md headings · 127 lines, 408 words
SKILL.md preview
---
name: unity-editor-tooling
description: |
  Unity Editor scripting — custom Inspectors, PropertyDrawers, EditorWindow,
  MenuItems, asset post-processors, Editor Coroutines, automated builds via
  `-batchmode -executeMethod`.

  USE WHEN: building tools for designers, custom Inspector UI, gizmos, scene
  validators, asset import hooks, editor menu commands, headless CI builds.

  DO NOT USE FOR: runtime UI (use `unity-input-ui`); test runner (use
  `unity-testing`).
allowed-tools: Read, Grep, Glob, Write, Edit
---

# Unity Editor Tooling

## Asmdef layout for editor code

```
Assets/
  Scripts/
    Runtime.asmdef          (no editor refs)
    Editor.asmdef           (Include Platforms = Editor only)
      depends on Runtime + UnityEditor
```

Editor code never ships in player builds — keep it isolated.

## Custom Inspector

```csharp
[CustomEditor(typeof(EnemySpawner))]
public class EnemySpawnerEditor : Editor {
    public override void OnInspectorGUI() {
        DrawDefaultInspector();

        var spawner = (EnemySpawner)target;
        EditorGUILayout.Space();
        if (GUILayout.Button("Spawn Test Wave")) {
            if (Application.isPlaying) spawner.SpawnTestWave();
            else Debug.LogWarning("Enter Play Mode first.");
        }
    }
}
```

Prefer **UI Toolkit Inspectors** (UXML/USS) for complex tools — better composition than IMGUI.

## PropertyDrawer

```csharp
[CustomPropertyDrawer(typeof(MinMaxRangeAttribute))]
public class MinMaxRangeDrawer : PropertyDrawer {
    public override void OnGUI(Rect r, SerializedProperty p, GUIContent l) {
        var attr = (MinMaxRangeAttribute)attribute;
        var min = p.FindPropertyRelative("min");
        var max = p.FindPropertyRelative("max");
        EditorGUI.MinMaxSlider(r, l, ref min.floatValue, ref max.floatValue, attr.Min, attr.Max);
    }
}
```

## EditorWindow

```csharp
public class LevelToolsWindow : EditorWindow {
    [MenuItem("Tools/Level Tools")]
    public static void Show() => GetWindow<LevelToolsWindow>("Level Tools");

    private void OnGUI() {
        if (GUILayout.Button("Bake Lighting")) Lightmapping.BakeAsync();
        if (GUILayout.Button("Validate Scene")) ValidateActiveScene();
    }
}
```

## Asset post-processor

Auto-fix import settings for new sprites:

```csharp
public class SpriteImporter : AssetPostprocessor {
    void OnPreprocessTexture() {
        if (!assetPath.Contains("/Sprites/")) return;
        var ti = (TextureImporter)assetImporter;
        ti.textureType = TextureImporterType.Sprite;
        ti.spritePixelsPerUnit = 32;
        ti.filterMode = FilterMode.Point;
        ti.textureCompression = TextureImporterCompression.Uncompressed;
    }
}
```

## Headless builds (`-batchmode`)

```csharp
public static class CIBuild {
    [MenuItem("Build/Build Windows")]
    public static void BuildWindows() {
        var opts = new BuildPlayerOptions {
            scenes = new[] { "Assets/Scenes/Boot.unity", "Assets/Scenes/Main.unity" },
            locationPathName = "Build/Win64/Game.exe",
            target = BuildTarget.StandaloneWindows64,
            options = BuildOptions.None,
        };
        var report = BuildPipeline.BuildPlayer(opts);
        if (report.summary.result != BuildResult.Succeeded)
            EditorApplication.Exit(1);
    }
}
```

CI invocation:

```bash
Unity -batchmode -nographics -quit \
  -projectPath . \
  -executeMethod CIBuild.BuildWindows \
  -logFile -
```

Combine with **Addressables.BuildPlayerContent()** before player build to prep content.

## Anti-patterns

| Anti-pattern | Fix |
|---|---|
| Editor code mixed in Runtime asmdef | Split asmdef; gate with `#if UNITY_EDITOR` for one-offs |
| Heavy logic in OnInspectorGUI | Cache, only recompute on `EditorUtility.SetDirty` events |
| `EditorPrefs` for project-shared state | Use `ProjectSettings` or assets in repo |
| Reflection-driven Inspectors with no fallback | Always provide DrawDefaultInspector path |

## Production checklist

- [ ] All custom tools have menu entries under `Tools/` namespace
- [ ] Asset post-processors enforce import settings (sprites, audio, models)
- [ ] CI builds run via `-batchmode -executeMethod`
- [ ] Editor analytics (`Analytics.RegisterEvent`) opt-in only, scrubbed of PII
- [ ] Editor coroutines used for long-running tools (don't freeze UI)

Versions

The database has no other skills named unity-editor-tooling.

Database snapshot: 13.11.2026 · package version c95e684d18fe (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100unity-editor-tools
    Unity 6 editor scripting and custom tools guide. Use when creating custom inspectors, EditorWindows, PropertyDrawers, Gizmos, Handles, menu items, or editor extensions. Covers SerializedObject/SerializedProperty pattern, AssetDatabase, and editor-only code with #if UNITY_EDITOR.…
  • 100uw-unity-editor-tools
    Generate custom editor tooling including Custom Inspectors, PropertyDrawers, EditorWindows, Gizmos, and Handles. Use when building designer-facing tools, spatial visualization, batch operations, or custom component UIs. Triggers on requests like "create a custom inspector", "add…
  • 98unity-editor-tool-developer
    Use when Codex should act as the Unity Editor Tool Developer specialist from Agency Agents. Unity editor automation specialist - Masters custom EditorWindows, PropertyDrawers, AssetPostprocessors, ScriptedImporters, and pipeline automation that saves teams hours per week
  • 100unity-run
    Use when running Unity from CLI for any purpose — builds, tests, method execution, asset imports. Handles Unity installation detection, batchmode execution, and log monitoring. Other unity-dev skills depend on this for CLI execution.
  • 100scenario-unity-expert
    Use when an agent drives Unity 6.3 (6000.3) on a Mac for any task: batch mode and -executeMethod jobs, a running editor (the user's GUI editor or a headless one), the Unity CLI and com.unity.pipeline, MCP servers, the Test Framework, command-line builds; when a batch run fails…
  • 88unity-batchmode
    Runs Unity without the editor UI - EditMode and PlayMode tests, player builds through a build script with a proper exit code, and compile checks - and reads the Unity log to report errors. Use when the user wants to build a Unity game from the terminal or CI, run Unity Test…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.