Feature/unity 6 upgrade

.claude/skills/uloop-clear-console/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: uloop-clear-console
+description: "Clear Unity Console entries. Use before compile, tests, or debugging when stale logs would hide the current result."
+---
+
+# npx --yes uloop-cli@2.2.0 clear-console
+
+Clear Unity console logs.
+
+## Usage
+
+```bash
+npx --yes uloop-cli@2.2.0 clear-console [--add-confirmation-message]
+```
+
+## Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `--add-confirmation-message` | boolean | `false` | Add confirmation message after clearing |
+
+## Global Options
+
+| Option | Description |
+|--------|-------------|
+| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
+
+## Examples
+
+```bash
+# Clear console
+npx --yes uloop-cli@2.2.0 clear-console
+
+# Clear with confirmation
+npx --yes uloop-cli@2.2.0 clear-console --add-confirmation-message
+```
+
+## Output
+
+Returns JSON with:
+- `Success` (boolean): Whether the clear operation succeeded
+- `ClearedLogCount` (number): Total number of log entries that were cleared
+- `ClearedCounts` (object): Breakdown by log type
+  - `ErrorCount` (number): Errors cleared
+  - `WarningCount` (number): Warnings cleared
+  - `LogCount` (number): Info logs cleared
+- `Message` (string): Description of the result; carries the failure summary when the operation fails (e.g. `"Failed to clear console: ..."`)
+- `ErrorMessage` (string): Currently always empty for this tool — read `Message` for failure details

.claude/skills/uloop-compile/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: uloop-compile
+description: "Compile the Unity project and report errors/warnings. Use after C# edits or when a full Domain Reload compile is needed."
+---
+
+# npx --yes uloop-cli@2.2.0 compile
+
+Execute Unity project compilation.
+
+## Usage
+
+```bash
+npx --yes uloop-cli@2.2.0 compile [--force-recompile <true|false>] [--wait-for-domain-reload <true|false>]
+```
+
+## Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `--force-recompile` | boolean value | `false` | Force full recompilation (triggers Domain Reload). Rarely needed — see "When to use --force-recompile" below. Pass `true` or `false`; bare flags are not accepted. |
+| `--wait-for-domain-reload` | boolean value | `false` | Wait until Domain Reload completes before returning. Pass `true` or `false`; bare flags are not accepted. |
+
+## When to use --force-recompile
+
+Almost never. Unity itself detects changed files — even when they were edited outside the
+Editor, a plain `npx --yes uloop-cli@2.2.0 compile` runs every recompilation the changes require. A forced full
+recompile can freeze the Editor for a long time on large projects, and with
+`--wait-for-domain-reload true` the response crosses a Domain Reload so `Success` comes back
+as `null`, making it useless as a verification step. The only legitimate use: surfacing
+warnings hidden by other asmdefs with a full build.
+
+## Global Options
+
+| Option | Description |
+|--------|-------------|
+| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
+
+## Examples
+
+```bash
+# Check compilation
+npx --yes uloop-cli@2.2.0 compile
+
+# Force full recompilation
+npx --yes uloop-cli@2.2.0 compile --force-recompile true
+
+# Force recompilation and wait for Domain Reload completion
+npx --yes uloop-cli@2.2.0 compile --force-recompile true --wait-for-domain-reload true
+
+# Wait for Domain Reload completion even without force recompilation
+npx --yes uloop-cli@2.2.0 compile --force-recompile false --wait-for-domain-reload true
+```
+
+## Output
+
+Returns JSON:
+- `Success`: boolean
+- `ErrorCount`: number
+- `WarningCount`: number
+
+## Troubleshooting
+
+Diagnose the failure mode before retrying.
+
+**Stale lock files** (CLI hangs or shows "Unity is busy" while Unity Editor *is* running):
+
+```bash
+npx --yes uloop-cli@2.2.0 fix
+```
+
+This removes any leftover lock files (`compiling.lock`, `domainreload.lock`, `serverstarting.lock`) from the Unity project's Temp directory. Then retry `npx --yes uloop-cli@2.2.0 compile`.
+
+**Unity Editor not running** (CLI returns a connection failure and no Unity process is alive):
+
+```bash
+npx --yes uloop-cli@2.2.0 launch
+```
+
+`npx --yes uloop-cli@2.2.0 launch` auto-detects the project at the current working directory and opens it in the matching Unity Editor version. After Unity finishes launching, retry `npx --yes uloop-cli@2.2.0 compile`.

.claude/skills/uloop-control-play-mode/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: uloop-control-play-mode
+description: "Control Unity Editor Play Mode. Use to start, stop, or pause Play Mode for runtime behavior checks and frame inspection."
+---
+
+# npx --yes uloop-cli@2.2.0 control-play-mode
+
+Control Unity Editor play mode (play/stop/pause).
+
+## Usage
+
+```bash
+npx --yes uloop-cli@2.2.0 control-play-mode [options]
+```
+
+## Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `--action` | string | `Play` | Action to perform: `Play`, `Stop`, `Pause` |
+
+## Global Options
+
+| Option | Description |
+|--------|-------------|
+| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
+
+## Examples
+
+```bash
+# Start play mode
+npx --yes uloop-cli@2.2.0 control-play-mode --action Play
+
+# Stop play mode
+npx --yes uloop-cli@2.2.0 control-play-mode --action Stop
+
+# Pause play mode
+npx --yes uloop-cli@2.2.0 control-play-mode --action Pause
+```
+
+## Output
+
+Returns JSON with the current play mode state:
+- `IsPlaying`: Whether Unity is currently in play mode
+- `IsPaused`: Whether play mode is paused
+- `Message`: Description of the action performed
+
+## Notes
+
+- Play action starts the game in the Unity Editor (also resumes from pause)
+- Stop action exits play mode and returns to edit mode
+- Pause action pauses the game while remaining in play mode
+- Useful for automated testing workflows
+
+- PlayMode entry may complete on the next editor frame. If a PlayMode-dependent command reports "PlayMode is not active" immediately after `--action Play`, wait briefly and retry.

.claude/skills/uloop-execute-dynamic-code/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: uloop-execute-dynamic-code
+description: "Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for scene, prefab, SerializedObject, AssetDatabase refresh/.meta generation, menu, or PlayMode automation."
+context: fork
+---
+
+# Task
+
+Execute the following request using `npx --yes uloop-cli@2.2.0 execute-dynamic-code`: $ARGUMENTS
+
+For basic selected GameObject discovery or property inspection, use `find-game-objects --search-mode Selected` before this tool. Use this tool after the built-in inspection tools are not enough or when you need to modify Unity state.
+
+## Workflow
+
+1. Read the relevant reference file(s) from the Code Examples section below
+2. Construct C# code based on the reference examples
+3. For multiline snippets, write the C# statements to a temporary `.csx` file and execute `npx --yes uloop-cli@2.2.0 execute-dynamic-code --code-file <path>`
+4. Use `npx --yes uloop-cli@2.2.0 execute-dynamic-code --code '<code>'` only for short one-line snippets
+5. If execution fails, adjust code and retry
+6. Report the execution result
+
+## Parameters
+
+- `--code '<code>'`: Inline C# statements to execute. Use this for one-line snippets only.
+- `--code-file <path>`: Read C# statements from a UTF-8 file. Prefer this for multiline snippets, especially on PowerShell, because Windows `.cmd` shims can lose lines from multiline inline arguments before `uloop` receives them.
+- **Shell quoting**: bash/zsh uses single quotes, for example `npx --yes uloop-cli@2.2.0 execute-dynamic-code --code 'using UnityEngine; return Mathf.PI;'`. PowerShell single-quoted strings can contain normal double quotes, for example `npx --yes uloop-cli@2.2.0 execute-dynamic-code --code 'Debug.Log("Hello!");'`.
+- `--parameters {}` (advanced, optional): Pass an object when reusing a snippet with varying data or when keeping values outside the code. Values are exposed as `parameters["param0"]`, `parameters["param1"]`, and so on. Omit this flag for most snippets, and pass an object instead of a JSON string.
+- `--compile-only true` (optional): Compile the snippet without executing it. Use this when you want Roslyn diagnostics before running new code.
+
+## Code Rules
+
+Write direct statements only — no class/namespace/method wrappers. Return is optional.
+
+```csharp
+using UnityEngine;
+float x = Mathf.PI;
+return x;
+```
+
+**Forbidden** — these will be rejected at compile time: `System.IO.*`, `AssetDatabase.CreateFolder`, creating/editing `.cs`/`.asmdef` files. Use terminal commands for file operations instead.
+
+## Output
+
+Returns JSON:
+- `Success`: boolean — overall execution success
+- `Result`: string — value of the snippet's `return` statement (empty when omitted)
+- `Logs`: string[] — execution diagnostics from the dynamic-code runner, not Unity Console entries
+- `CompilationErrors`: object[] — Roslyn diagnostics with `Message`, `Line`, `Column`, `ErrorCode`, optional `Hint` and `Suggestions`
+- `ErrorMessage`: string — top-level failure summary (empty on success)
+- `Error`: string — alias of `ErrorMessage`
+- `SecurityLevel`: string — dynamic-code security level active for the request
+- `UpdatedCode`: string|null — the wrapped form actually compiled (handy when debugging using-statement reordering)
+- `DiagnosticsSummary`: string|null — compact summary when diagnostics are available
+- `Diagnostics`: object[] — structured diagnostics; same shape as `CompilationErrors`, usually populated together with it
+
+Use `npx --yes uloop-cli@2.2.0 get-logs` to retrieve `Debug.Log`, `Debug.LogWarning`, and `Debug.LogError` messages emitted by the snippet. On `Success: false`, inspect `CompilationErrors` first. If empty, read `ErrorMessage` (and `Logs` for extra context) — the failure may be a runtime exception, security violation, cancellation, or an "execution in progress" rejection, all of which return empty `CompilationErrors`. Both EditMode and PlayMode are supported targets — the snippet runs in whichever mode the Editor is currently in.
+
+## Code Examples by Category
+
+For detailed code examples, refer to these files:
+
+- **Prefab operations**: See [references/prefab-operations.md](references/prefab-operations.md)
+  - Create prefabs, instantiate, add components, modify properties
+- **Material operations**: See [references/material-operations.md](references/material-operations.md)
+  - Create materials, set shaders/textures, modify properties
+- **Asset operations**: See [references/asset-operations.md](references/asset-operations.md)
+  - Find/search assets, duplicate, move, rename, load
+- **ScriptableObject**: See [references/scriptableobject.md](references/scriptableobject.md)
+  - Create ScriptableObjects, modify with SerializedObject
+- **Scene operations**: See [references/scene-operations.md](references/scene-operations.md)
+  - Create/modify GameObjects, set parents, wire references, load scenes
+- **Batch operations**: See [references/batch-operations.md](references/batch-operations.md)
+  - Bulk modify objects, batch add/remove components, rename, layer/tag/material replacement
+- **Cleanup operations**: See [references/cleanup-operations.md](references/cleanup-operations.md)
+  - Detect broken scripts, missing references, unused materials, empty GameObjects
+- **Undo operations**: See [references/undo-operations.md](references/undo-operations.md)
+  - Undo-aware operations: RecordObject, AddComponent, SetParent, grouping
+- **Selection operations**: See [references/selection-operations.md](references/selection-operations.md)
+  - Get/set selection, multi-select, filter by type/editability
+- **PlayMode automation (zsh)**: See [references/playmode-automation-zsh.md](references/playmode-automation-zsh.md)
+  - Click UI buttons, invoke methods, set fields, tool combination workflows for zsh users
+- **PlayMode automation (PowerShell)**: See [references/playmode-automation-powershell.md](references/playmode-automation-powershell.md)
+  - Click UI buttons, invoke methods, set fields, tool combination workflows for PowerShell users
+- **PlayMode UI controls**: See [references/playmode-ui-controls.md](references/playmode-ui-controls.md)
+  - InputField, Slider, Toggle, Dropdown, drag & drop simulation, list all UI controls
+- **PlayMode inspection**: See [references/playmode-inspection.md](references/playmode-inspection.md)
+  - Scene info, game state via reflection, physics state, raycast checks, GameObject search, position/rotation