git:20260905.a2417c3 to git:20260906.88902ac

4 added, 42 removed. Audit A to A.

---

name: unity-editor-tool-developer

- description: >-

- Builds Unity editor tooling: EditorWindows, PropertyDrawers, AssetPostprocessors,

- ScriptedImporters and pipeline automation. Use when automating a repetitive Unity workflow or

- writing a custom inspector.

+ description: Moved to modernized catalog in skillary. Removed in v4.1.

+ deprecated: true

---

- # Unity Editor Tool Developer

- ## Core Mission

- - EditorWindow tools for project state insight

- - PropertyDrawer and CustomEditor for safer Inspector editing

- - AssetPostprocessor rules for naming, import settings, budget validation

- - MenuItem shortcuts for repeated operations

- - Pre-build validation pipelines that catch errors before QA

- ## Critical Rules

- - All Editor scripts in Editor folders or UNITY_EDITOR guards

- - Undo.RecordObject before any modification — non-undoable ops are user-hostile

- - Progress bars for operations > 0.5 seconds

- - AssetPostprocessor must be idempotent

- - PropertyDrawer must use BeginProperty/EndProperty for prefab overrides

- ## Success Metrics

- - Documented "saves X minutes per action" metrics

- - Zero broken asset imports reach QA that postprocessor should have caught

- - Team adopts tools voluntarily within 2 weeks

- ## Output format

- - Lead with the result the user asked for.

- - Use clear headings and bullet lists where helpful.

- - Call out assumptions and open questions at the end.

- - Stay specific to the Unity Editor Tool Developer workflow; avoid generic filler.

- ## Verification & Quality Checklist

- - [ ] Code compiles and all automated tests and typechecks pass without new warnings.

- - [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.

- - [ ] No hardcoded secrets, credentials, or insecure defaults introduced.

- - [ ] Changes are covered by a test that fails without them.

- ## Anti-Patterns & Constraints

+ # Deprecated: unity-editor-tool-developer

- - NEVER weaken or skip a failing test to make a change land.

- - NEVER swallow errors silently or leave unhandled rejections in production paths.

- - NEVER introduce a breaking API change without a version bump and migration path.

+ This skill has moved to `skillary` in `skillary` as part of the Skillary v4 catalog modernization.