chore(release): v0.19.0

.claude-plugin/plugins/unity-cli/agents/unity-helper.md

@@ -32,7 +32,7 @@ You are a Unity automation specialist. Execute multi-step workflows using `unity
 
 ### Code Scaffold
 
-1. Create class with `create_class` or `create_csharp_file` → update code with `write_csharp_file` or `apply_csharp_edits` → build or update index → check compilation state
+1. Create the script with `create_csharp_file` (LSP-validated; `create_class` is only an empty-class shortcut on the same LSP path) → update code with `write_csharp_file`, `apply_csharp_edits`, or symbol edits → build or update index → check compilation state → fix compile errors with the same LSP write tools, never with direct file edits
 
 ### Test Cycle
 

.claude-plugin/plugins/unity-cli/skills/unity-2d-sprite-tilemap/references/runtime-checklist.md

@@ -35,7 +35,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-audio-setup/references/runtime-checklist.md

@@ -35,7 +35,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-cli-usage/references/runtime-checklist.md

@@ -52,7 +52,7 @@ completion and inspect that call's exit code.
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-csharp-edit/SKILL.md

@@ -1,14 +1,19 @@
 ---
 name: unity-csharp-edit
-description: Implement, fix, and refactor Unity C# code with unity-cli write tools. Use when the user wants to change behavior in .cs files, create or rewrite scripts, update multiple C# files together, rename a symbol, add or remove members, or change project or package settings as part of a code change. Do not use for read-only inspection with no planned edit; use `unity-csharp-navigate` instead.
+description: Implement, fix, and refactor Unity C# code with unity-cli write tools. Use when the user wants to change behavior in .cs files, create a new script, class, MonoBehaviour or ScriptableObject, rewrite scripts, fix compile errors, update multiple C# files together, rename a symbol, add or remove members, or change project or package settings as part of a code change. Do not use for read-only inspection with no planned edit; use `unity-csharp-navigate` instead.
 allowed-tools: Bash(unity-cli:*), Read, Grep, Glob, Edit, Write
 metadata:
   author: akiojin
-  version: 0.3.0
+  version: 0.3.2
   category: code
   triggers:
     - csharp
     - script
+    - new script
+    - class
+    - monobehaviour
+    - scriptableobject
+    - compile error
     - rename
     - refactor
     - symbol
@@ -31,7 +36,8 @@ Implement Unity C# changes with `unity-cli` as the primary write path. Prefer th
 ## Use When
 
 - The user intends to change C# behavior in `.cs` files.
-- The user wants to create or rewrite scripts (single or coordinated multi-file).
+- The user wants to create a new script, class, `MonoBehaviour`, or `ScriptableObject`, or rewrite scripts (single or coordinated multi-file).
+- The user wants to fix C# compile errors.
 - The user asks for a symbol rename, member add/remove, or refactor.
 - The user changes project or package settings as part of a code change.
 
@@ -44,22 +50,38 @@ Implement Unity C# changes with `unity-cli` as the primary write path. Prefer th
 
 ## Preferred Flow
 
-1. Decide the write shape: symbol edit, full-file write, multi-file write, or settings change.
+1. Decide the write shape: new file, symbol edit, full-file write, multi-file write, or settings change. Always write `.cs` files through the LSP write tools (`create_csharp_file`, `write_csharp_file`, `apply_csharp_edits`, symbol edits) so the text is validated before it lands; do not hand-write `.cs` files with direct file edits unless the LSP write path fails (see LSP Write Failure Fallback).
 2. Read only the minimum context with `read`, `get_symbols`, `find_symbol`, or `find_refs`.
 3. Preview risky symbol edits with `apply: false`.
 4. Apply with `refresh`, `waitForCompile`, and `updateIndex` when later steps depend on clean diagnostics.
 5. Inspect `changedFiles`, `changedSymbols`, and `diagnostics`; fix compilation issues before unrelated follow-up.
 
 ```bash
+unity-cli raw create_csharp_file --json '{"relative":"Assets/Scripts/EnemyAI.cs","text":"using UnityEngine;\n\npublic class EnemyAI : MonoBehaviour\n{\n}\n","validate":true,"apply":true,"waitForCompile":true,"updateIndex":true}'
 unity-cli raw get_symbols --json '{"path":"Assets/Scripts/Player.cs"}'
 unity-cli raw rename_symbol --json '{"relative":"Assets/Scripts/Player.cs","namePath":"Player/Jump","newName":"Leap","apply":false}'
 unity-cli raw apply_csharp_edits --json '{"files":[{"relative":"Assets/Scripts/IPlayerMover.cs","newText":"public interface IPlayerMover { void Move(); }\n"}],"validate":true,"apply":true,"waitForCompile":true,"updateIndex":true}'
 unity-cli raw get_compilation_state --json '{}'
 ```
 
+## LSP Write Failure Fallback
+
+Use this only when an LSP write tool fails: the LSP server fails to start, the call times out, or the tool returns an unsupported-edit error. Retry once if the failure looks transient; do not stop the task.
+
+1. Make the same change with your own `Edit` (existing file) or `Write` (new file). Keep it identical in scope to the intended LSP write.
+2. Refresh and confirm compilation with `unity-cli`:
+   ```bash
+   unity-cli raw refresh_assets --json '{}'
+   unity-cli raw get_compilation_state --json '{}'
+   ```
+   Fix any reported errors before continuing; if the Editor is unreachable, say so and leave compilation unconfirmed.
+3. In your work report, state that the LSP path was not used, which tool failed, and why (error code or message).
+
 ## Examples
 
 - "Implement dash cooldown in `PlayerController.cs` and update the related tests."
+- "Create an `EnemyAI` MonoBehaviour in `Assets/Scripts/AI`."
+- "Fix the compile error in `PlayerController.cs`."
 - "Rename `Jump` to `Leap` across the player package without breaking serialized field names."
 - "Create a new editor utility script and change the matching project setting."
 - "Refactor an interface, its implementation, and the tests in one coordinated write."

.claude-plugin/plugins/unity-cli/skills/unity-csharp-edit/references/file-write-recipes.md

@@ -32,11 +32,10 @@ Recommended options:
 
 ## Choose `create_csharp_file` When
 
-- You need a new file that is not just a standard class shell.
-- The file should contain an interface, enum, test fixture, editor utility, or multiple types.
+- You need any new `.cs` file: a class, `MonoBehaviour`, `ScriptableObject`, interface, enum, test fixture, editor utility, or multiple types.
 - You want the same validated write contract as `write_csharp_file`.
 
-Use `create_class` only when the class template itself is the useful shortcut.
+`create_class` is a shortcut for an empty class shell (`name`, `folder`, optional `namespace` / `inherits`). It writes through the same LSP path as `create_csharp_file`, so both are safe; prefer `create_csharp_file` when the file needs members.
 
 ## Choose `apply_csharp_edits` When
 
@@ -56,6 +55,7 @@ Keep the `files` array minimal and coherent. If files are unrelated, split the t
 ## Example Paths
 
 ```bash
+unity-cli raw create_csharp_file --json '{"relative":"Assets/Scripts/EnemyAI.cs","text":"using UnityEngine;\n\npublic class EnemyAI : MonoBehaviour\n{\n}\n","validate":true,"apply":true,"waitForCompile":true,"updateIndex":true}'
 unity-cli raw replace_symbol_body --json '{"relative":"Assets/Scripts/PlayerController.cs","namePath":"PlayerController/Move","body":"{ transform.position += direction * speed * Time.deltaTime; }","apply":false}'
 unity-cli raw write_csharp_file --json '{"relative":"Assets/Scripts/PlayerController.cs","newText":"using UnityEngine;\n\npublic sealed class PlayerController : MonoBehaviour {}\n","validate":true,"apply":true,"waitForCompile":true,"updateIndex":true}'
 unity-cli raw apply_csharp_edits --json '{"files":[{"relative":"Assets/Scripts/IPlayerMover.cs","newText":"public interface IPlayerMover { void Move(); }\n"},{"relative":"Assets/Scripts/PlayerMover.cs","newText":"public sealed class PlayerMover : IPlayerMover { public void Move() {} }\n"},{"relative":"Assets/Tests/EditMode/PlayerMoverTests.cs","newText":"using NUnit.Framework;\n\npublic class PlayerMoverTests {}\n"}],"validate":true,"apply":true,"waitForCompile":true,"updateIndex":true}'

.claude-plugin/plugins/unity-cli/skills/unity-csharp-edit/references/lsp-write-safety.md

@@ -25,7 +25,15 @@
 3. Run `get_compilation_state` for non-trivial edits or when diagnostics are still unclear.
 4. Report and fix real diagnostics before attempting unrelated follow-up changes.
 
-## Class Creation
+## New Files
 
-- Use `create_class` for new files instead of hand-writing boilerplate when possible.
+- Use `create_csharp_file` for every new `.cs` file (classes, `MonoBehaviour`, `ScriptableObject`, interfaces, enums, tests). It validates the text through LSP before writing.
+- `create_class` (`name`, `folder`, optional `namespace` / `inherits`) is a shortcut that renders an empty class shell and writes it through the same LSP path as `create_csharp_file`. Prefer `create_csharp_file` when the file needs any members.
+- Do not create or edit `.cs` files with direct file writes; they skip LSP validation. The only exception is the `LSP Write Failure Fallback` in `SKILL.md`.
 - Use `validate_text_edits` when constructing larger manual replacements.
+
+## Compile Error Fixes
+
+- Read the error `file` / `line` from `get_compilation_state` or `editorLog.compileErrors[]`.
+- Fix it with the smallest LSP write: `replace_symbol_body` for one member, `write_csharp_file` for one file, `apply_csharp_edits` when several files must change together.
+- These tools run locally, so they work in `SAFE_MODE` when the bridge is not loaded.

.claude-plugin/plugins/unity-cli/skills/unity-development-loop/references/runtime-checklist.md

@@ -22,7 +22,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-gameobject-edit/SKILL.md

@@ -57,6 +57,19 @@ Modify existing GameObjects and their components in an already-prepared scene. T
 4. Reserve `delete_gameobject` and `remove_component` for confirmed scopes.
 5. Save the scene after destructive or bulk updates so reloads do not lose work.
 
+## Target Parameter Names
+
+The key that names the target object differs by tool. A wrong key fails locally with `INVALID_ARGUMENT` (`$.<key> is required` or `$.<key> is not allowed`) before reaching Unity.
+
+| Key              | Tools                                                                                             |
+| ---------------- | ------------------------------------------------------------------------------------------------- |
+| `path`           | `modify_gameobject` (its `name` renames), `delete_gameobject` (`paths` for several)               |
+| `gameObjectPath` | `add_component`, `modify_component`, `set_component_field`, `remove_component`, `list_components` |
+| `name`           | `find_gameobject`, `create_gameobject` (parent via `parentPath`)                                  |
+| `gameObjectName` | read-only queries such as `get_component_values`; see `unity-scene-inspect`                       |
+
+When unsure, read the schema: `unity-cli tool schema <tool_name> --output json`.
+
 ```bash
 unity-cli raw modify_gameobject --json '{"path":"/Player","name":"Hero","active":true}'
 unity-cli raw add_component --json '{"gameObjectPath":"/Player","componentType":"Rigidbody"}'

.claude-plugin/plugins/unity-cli/skills/unity-localization/references/runtime-checklist.md

@@ -35,7 +35,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-project-bootstrap/references/runtime-checklist.md

@@ -35,7 +35,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.

.claude-plugin/plugins/unity-cli/skills/unity-scene-inspect/SKILL.md

@@ -44,6 +44,19 @@ Inspect scene hierarchy, find objects, and read component data without mutating
 3. Inspect targets with `get_gameobject_details`, `get_component_values`, or animator queries.
 4. Use `analyze_scene_contents` with `includeInactive` for broad audits.
 
+## Target Parameter Names
+
+Read-only queries name their target differently from the edit tools. A wrong key fails locally with `INVALID_ARGUMENT` before reaching Unity.
+
+| Key                        | Tools                                                                                              |
+| -------------------------- | -------------------------------------------------------------------------------------------------- |
+| `gameObjectName`           | `get_component_values`, `get_object_references`, `get_animator_state`, `get_animator_runtime_info` |
+| `gameObjectName` or `path` | `get_gameobject_details`                                                                           |
+| `name`                     | `find_gameobject`                                                                                  |
+| `rootPath`                 | `get_hierarchy`                                                                                    |
+
+`gameObjectName` takes a name or a hierarchy path such as `/Root/Child`. Edit tools use `path` or `gameObjectPath` instead; see `unity-gameobject-edit`. When unsure: `unity-cli tool schema <tool_name> --output json`.
+
 ```bash
 unity-cli raw get_hierarchy --json '{"nameOnly":true}'
 unity-cli raw find_gameobject --json '{"name":"Player"}'

.claude-plugin/plugins/unity-cli/skills/unity-ui-toolkit-build/references/runtime-checklist.md

@@ -35,7 +35,7 @@
 
 - A failed `system ping` does not prove the Editor is closed. Run `unity-cli doctor --output json` (add `--project-path <dir>` outside the project) before any fallback such as hand-editing YAML.
 - Act on the `diagnosis` code:
-  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) by editing the file directly, then let Unity recompile or restart the Editor.
+  - `SAFE_MODE` / `COMPILE_ERRORS`: the bridge is not loaded. Fix each `editorLog.compileErrors[]` entry (`file`, `line`, `code`) with the LSP write tools (`apply_csharp_edits`, `replace_symbol_body`, `write_csharp_file`); they run locally and do not need the bridge. Then let Unity recompile or restart the Editor.
   - `BRIDGE_NOT_INSTALLED`: run `unity-cli setup` (or `unity-cli bridge install`) to add `com.akiojin.unity-cli-bridge` to `Packages/manifest.json`.
   - `PORT_IN_USE`: `port.listenerPid` / `port.listenerProcess` hold the port. Stop it or change the bridge port and pass the same `--port`.
   - `EDITOR_NOT_RUNNING`: start the Editor for the project and wait for import to finish.