Uw 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 gizmos", "build an editor window", "make this component designer-friendly", "add a debug visualization", "create a level editor tool", "add a property drawer", "make a batch rename tool", or any editor tooling work. Always uses SerializedProperty and Undo for safety.
Install
npx skills add devdavv/unity-ai-workflow --skill uw-unity-editor-toolsgit clone --depth 1 https://github.com/devdavv/unity-ai-workflow.git /tmp/unity-ai-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/unity-ai-workflow/.claude/skills/uw-unity-editor-tools ~/.claude/skills/uw-unity-editor-toolsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Unity Editor Tools
Generate editor tooling that follows Unity best practices.
## Before You Start
1. Read `docs/ProjectConfig.yaml` for:
- `unity_version` — UI Toolkit editor UI requires 2022.2+ (all Unity 6+ projects qualify).
- `ui_system` — if `"UIToolkit"` or `"Mixed"`, prefer UI Toolkit for editor UIs too (consistent approach).
- `mcp.unity_mcp` — if `true`, call `refresh_unity` after creating files.
2. Check if the feature has an `Editor/` asmdef — if not, create one. The Editor asmdef must reference the Runtime asmdef and have `Editor` as its only Include Platform.
3. Read `docs/NAMING_CONVENTIONS.md` for editor script naming.
## Core Rules (Non-Negotiable)
```csharp
// ALWAYS: Use SerializedProperty for inspector fields
SerializedProperty _healthProp;
void OnEnable() => _healthProp = serializedObject.FindProperty("_health");
// NEVER: Direct field access (breaks multi-edit, prefabs, undo)
((MyComponent)target)._health = EditorGUILayout.FloatField(((MyComponent)target)._health);
```
```csharp
// ALWAYS: Record undo before modifications
Undo.RecordObject(target, "Changed patrol point");
myComponent.patrolPoints[i] = newPos;
// NEVER: Modify without undo
myComponent.patrolPoints[i] = newPos;
```
```csharp
// ALWAYS: Mark dirty after changes in tools
EditorUtility.SetDirty(target);
// ALWAYS: Apply modified properties in inspectors
serializedObject.ApplyModifiedProperties();
```
## Tool Selection
| Need | Tool | Reference |Details
- Skill name
uw-unity-editor-tools- Repository
- devdavv/unity-ai-workflow
- Path
.claude/skills/uw-unity-editor-tools/SKILL.md- License
- MIT
- Repo updated
- 1 April 2026
FAQ
What does the Uw Unity Editor Tools skill do?
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 gizmos", "build an editor window", "make this component designer-friendly", "add a debug visualization", "create a level editor tool", "add a property drawer", "make a batch rename tool", or any editor tooling work. Always uses SerializedProperty and Undo for safety.
How do I install the Uw Unity Editor Tools skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add devdavv/unity-ai-workflow --skill uw-unity-editor-tools. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Uw Unity Editor Tools popular?
It lives in devdavv/unity-ai-workflow, which has 47 GitHub stars and 6 forks.
Related skills
Uw Code Review
47devdavv/unity-ai-workflow
Pre-commit code quality review for Unity C# code. Checks against Rules, CODING_STANDARDS.md, NAMING_CONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code", "check my implementation", "pre-commit review", "code review", "check before commit", "is this ready to commit", "review my changes", or any request to validate code quality before committing.
Uw Dependency Injection
47devdavv/unity-ai-workflow
Opt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, an
Uw Game Feel Integrator
47devdavv/unity-ai-workflow
Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Mat
Jta
24ckanner/agent-skills
Translate JSON i18n files to multiple languages with AI-powered quality optimization. Use when user mentions translating JSON, i18n files, internationalization, locale files, or needs to convert language files to other languages.
Neovim Rpc
49sodiumjoe/dotfiles
Interact with a running neovim instance over RPC — open files, show diffs, execute Lua. Use when you need to open a file in the user's editor, show a vimdiff, or run arbitrary Lua in neovim. Requires $NVIM or $NVIM_SOCKET_PATH to be set.
App Localization
40tddworks/claude-skills
iOS/macOS app localization management for Tuist-based projects with .strings files. Use when: (1) Adding new translation keys to modules, (2) Validating .strings files for missing/duplicate keys, (3) Syncing translations across languages, (4) AI-powered translation from English to other locales, (5) Checking placeholder consistency (%@, %d), (6) Generating localization reports, (7) Updating Swift code to use localized strings instead of hardcoded text.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.