[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMHAWTW072W05ESA09WY6B":3,"skill-same:01M7CMHAWTW072W05ESA09WY6B":112},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CMHAWTW072W05ESA09WY6B","unity-debug",null,"Verify a change in the running game: Editor.log, screenshots, tests; exit 0 but nothing ran.","tipoLi5890\u002Funity-dev-skills","tipoLi5890","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177803612?v=4","01M7CMD7DHGZ09CB53CRFHAA34","Li, ching yu","01M7CMD7E70K5RAHWWZVYX9YMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-debug\ndescription: >-\n  Verify a change in the running game: Editor.log, screenshots, tests; exit 0\n  but nothing ran.\n---\n\n# unity-debug — verify it yourself, and check the instrument first\n\nThe agent cannot see the Game view. **Never iterate via \"add a log → ask for a screenshot →\nguess\".** Unity will run itself, report to a log, and hand you PNGs you can read.\n\nThere is one rule above all the technique, and it is the one that costs the most when broken:\n\n> **A number is worthless until you know the run that produced it happened.**\n> Exit code 0 does not mean Unity started. A results file does not mean it is *this* run's results\n> file. A measurement does not mean the thing measured moved.\n\nA stale results XML reads \"6\u002F6 passed\" while Unity fails to start on every run. Start at\n`reference\u002Fharness-trust.md`; the guard is one line of `rm`.\n\n## Symptom → where to look\n\n| The report | Go to |\n|---|---|\n| \"exit 0 but no results file\", a run that did nothing, \"the tests are green but nothing was verified\" | `reference\u002Fharness-trust.md` |\n| \"which test failed\", `failed=0` that checked nothing | `reference\u002Ftest-verdicts.md` |\n| \"verify the fix works\" in the running game | *The four loops* |\n| \"the player won't move\", \"nothing happens when I press Play\" | `reference\u002Flog-triage.md`, then `reference\u002Feditor-control.md` |\n| \"the UI is shaking \u002F flickering\", anything temporal | `reference\u002Fmotion-and-timing.md`, `reference\u002Fvisual-checks.md` |\n| Green in the Editor, broken in a build | `reference\u002Fplayer-tests.md` |\n| Only breaks on the phone | skill `unity-device-testing` |\n| Anything else | *Load what the situation needs* |\n\n## The four loops\n\n**0 · Live-Editor loop** — fastest of all when the project has the Pipeline package: a running\nEditor answers `unity command` without recompiling or reloading the domain. Everything below\npays a cold start; this one does not. → `reference\u002Feditor-control.md`\n\n**1 · Log loop** — fastest when a human is at the keyboard. Instrument with a grep-able prefix, ask\nfor one Play, read Editor.log. → `reference\u002Flog-triage.md`\n\n**2 · CLI loop** — no human needed. `-batchmode` for compile and logic, ~20 s warm.\n→ `reference\u002Fcli-harness.md`\n\n**3 · Visual loop** — windowed `-runTests`, walk the whole flow, drop numbered PNGs, read them.\nCatches everything assertions cannot: overlap, clipping, contrast, wrong aspect.\n→ `reference\u002Fvisual-checks.md`\n\nBatchmode **cannot** screenshot (no end of frame). Windowed can, and IMGUI shows up in the capture.\nA live Editor can too, via `unity command screenshot` — which is loop 0's answer to loop 3.\n\nLoops 2 and 3 need not queue on one Editor: the lock is per project folder, so clone *lanes* run\nseveral Editors on one machine at once. → `reference\u002Fparallel-runs.md`\n---\n\n## Load what the situation needs\n\n| The situation | Read |\n|---|---|\n| About to trust a test result, or something reads as impossible | `reference\u002Fharness-trust.md` |\n| A run's verdict: which test failed, `failed=0` that checked nothing, state leaking between runs | `reference\u002Ftest-verdicts.md` |\n| Running Unity headless; tests not found; asmdef errors | `reference\u002Fcli-harness.md` |\n| Iterating more than twice; want to poke a live Editor; `unity command` won't connect; Safe Mode | `reference\u002Feditor-control.md` |\n| Need to SEE a screen; layout, contrast or cropping suspected | `reference\u002Fvisual-checks.md` |\n| The look changed and nobody meant it to; a screenshot diff against baselines, with an exit code | `reference\u002Fvisual-checks.md` (golden images) · `scripts\u002Fgolden_diff.py` |\n| The suite takes too long for one Editor; several agents want Unity at once; host and client in two Editors | `reference\u002Fparallel-runs.md` · `scripts\u002Flanes.sh` |\n| Other agents, Blender or a second project share the machine; a timing test red only sometimes; pipeline work that needs an Editor but not the game | `reference\u002Fparallel-runs.md` → \"The machine is shared\", \"A lab project\" |\n| Cyan materials or a frozen object on the first Play only; a capture that skews a timing number; a motion clip to review | `reference\u002Funity-gotchas.md` §22–23 · `reference\u002Fmotion-and-timing.md` |\n| A batchmode or EditMode tool samples a clip and every frame reads the bind pose | `reference\u002Funity-gotchas.md` §24 |\n| Briefing several agents: who owns lane 0, the Editor cap, push and hook rules | skill `unity-game-brief` → `templates\u002FAGENT_BRIEF.md` |\n| Green in the Editor, broken in a build: stripping, platform defines, init order — tests run inside a player | `reference\u002Fplayer-tests.md` |\n| \"It shakes \u002F flickers \u002F shimmers\"; anything temporal | `reference\u002Fmotion-and-timing.md` |\n| Runtime misbehaviour with a human pressing Play; device triage | `reference\u002Flog-triage.md` |\n| Phantom collisions, invisible objects, hitboxes, import weirdness | `reference\u002Funity-gotchas.md` |\n| The game cannot boot into the moment under test; nothing readable says what state it is in; a feel report with nothing to measure | skill `unity-play-harness` |\n| \"It is slow\", hitches, draw calls or GC — numbers you can compare across a change | skill `unity-profiling` |\n| A collision or trigger that never fires, tunnelling, a raycast that misses | skill `unity-physics-3d` · `unity-physics-2d` |\n| Post-processing set but not visible; reviewing a renderer feature | skill `unity-render-urp` |\n| A Scene-view or camera PNG for a before\u002Fafter comparison, outside a test run | skill `unity-urp-migration` → `resources\u002FEditor\u002FSceneCapture.cs` |\n| \"Find \u002F where is \u002F what references X\" — one query over project assets or the loaded scenes, rather than a script | skill `unity-search` |\n| Installing editors, licences, templates, MCP wiring, CI invocation | skill `unity-cli` |\n| An agent that will not move or path around something | skill `unity-navigation` |\n| Building the game's UI rather than debugging it | skill `unity-game-ui` |\n\n`resources\u002FDevDebug.cs` is a project-agnostic drop-in probe. Copy into `Assets\u002F`, attach,\n**delete when finished.** A permanent, contract-shaped probe that ships with the game and every run\ncan read is a different thing — that one is `unity-play-harness`.\n\n---\n\n## Discipline\n\n- **List, never recall.** Command names, template ids and package ids are defined by the Editor\n  and the registry, not by your memory of them. `unity command --format json`, `unity templates\n  list`, `Client.SearchAll()` — one call is cheaper than one wrong guess.\n- **Clone lanes run read-only work; anything that writes assets runs on lane 0.** Two Editors\n  importing into one `Assets\u002F` race on `.meta` files. → `reference\u002Fparallel-runs.md`.\n- **Delete the results file before every run.** A missing file is an obvious failure; a stale one\n  is a silent lie.\n- **Never pipe a test driver into `tail` or `head`.** The shell then reports the *pipe's* exit\n  status, so a driver that printed `exit=2 … failed=\"2\"` comes back to you as \"exited with code 0\".\n- **Read `inconclusive=` next to `failed=`.** `Assert.Inconclusive` leaves `failed=\"0\"`, so a whole\n  test class can skip itself — usually exactly when the assets it guards are missing — and the run\n  still reads green. → `reference\u002Ftest-verdicts.md`.\n- **Reset PlayerPrefs and persistent data in `[SetUp]`.** They survive between PlayMode runs, which\n  is how a suite passes on CI and fails on the developer's machine, and how \"the same test\" produces\n  two different screenshots.\n- **Log the state next to every screenshot** (`[SHOT] 04_countdown state=Countdown`) so a capture\n  that photographed the wrong moment cannot pass unnoticed.\n- **Print the numbers a test asserts on.** A green tick says a test passed; a logged\n  `world width=0.50 laneSpacing=1.30` says why, and keeps saying it after the next change.\n- **At most two Editors on the machine, whatever project they belong to**, and look at the load\n  (`uptime`, top of `ps`) before believing any millisecond. Another agent's Blender job made frame\n  times 2 to 5 times high and turned a smoke test red. `lanes.sh` queues at `MAX_UNITY`.\n- **Median and worst, never just worst** — one spike and a constant vibration are different faults.\n- **When a measurement contradicts the code, suspect the measurement.** Dump the pixels. Take a\n  whole-frame diff. The constants are rarely the liar.\n- **Re-run before calling a failure a regression.** Timing-sensitive tests exist, and a graphics\n  change can tip one over without touching gameplay. Say so plainly rather than inventing a cause.\n\n## Scope — what this skill does NOT do\n\n| Not here | Go to |\n|---|---|\n| Installing editors, licences, templates, CI invocation | `unity-cli` |\n| Building or signing an artifact | `unity-android-release` · `unity-web-release` |\n| A collision or trigger that never fires | `unity-physics-3d` · `unity-physics-2d` |\n| An agent that will not move | `unity-navigation` |\n| Post-processing that will not appear | `unity-render-urp` |\n| Designing the UI rather than verifying it | `unity-game-ui` |\n| Building the game so an agent can drive and read it: probes, named situations, journey tests | `unity-play-harness` |\n| Frame-time windows, profiler counters, a before\u002Fafter table | `unity-profiling` |\n| Deciding what to build first: the brief, the constraints, the first interaction | `unity-game-brief` |\n| \"Find \u002F where is \u002F what references X\" answered as a Unity Search query rather than a scripted audit | `unity-search` |\n| Verifying on a real phone rather than in the editor: adb \u002F devicectl drivers, a probe scene, a human in the loop | `unity-device-testing` |\n\n## Running PlayMode tests edits your project\n\nSide effects that all get committed if nobody looks:\n\n> **The test framework flips `runInBackground` to 1 in `ProjectSettings.asset` and does not put\n> it back.** A `git status` after a green test run is not clean, and the diff has nothing to do\n> with what you were testing.\n\n> **Restore that one LINE, never the whole file.** `git checkout -- ProjectSettings\u002FProjectSettings.asset`\n> is the obvious cleanup and it is destructive: it silently discards any Player Settings written\n> since the last commit — a setup step's target SDK level and app icons, say — which then have to\n> be regenerated. Restore surgically instead — and note that any *other* script running the suite\n> (a release build that tests before packaging) needs the same restore:\n>\n> ```bash\n> grep -q \"^  runInBackground: 1$\" ProjectSettings\u002FProjectSettings.asset && \\\n>   sed -i '' 's\u002F^  runInBackground: 1$\u002F  runInBackground: 0\u002F' ProjectSettings\u002FProjectSettings.asset\n> ```\n>\n> (BSD `sed` on macOS needs the empty `''` after `-i`; GNU `sed` takes `-i` alone.)\n\n> **A crashed run leaves files in the project.** `Assets\u002FInitTestScene\u003Cguid>.unity` plus its `.meta`\n> (the runner's temp scene) and a `mono_crash.mem.\u003Cpid>.\u003Cn>.blob` dump in the project root — both\n> swept up by the next `git add -A`. Ignore `Assets\u002FInitTestScene*` and `mono_crash.*`.\n\n> **Killing an Editor before a test run leaves `Temp\u002F` in a state that aborts the next one** with\n> *\"Scripts have compiler errors\"* and **no `error CS` line in the log** — the compiler never ran.\n> → `reference\u002Feditor-control.md`.\n\nSo the run protocol is: delete the results file, run, **then `git status`** — and revert what the\nharness changed before reporting anything as done.\n\n## Cleanup before handing back a \"clean\" build\n\n- Remove `[RUN]`\u002F`[DBG]` logs and per-frame dumps; remove `DevDebug.cs` and detach it.\n- Remove on-screen debug panels and debug-only serialized fields.\n- Keep the **fixes** found while debugging; delete only the **instrumentation**.\n- Leave the harness in a green, honestly-verified state — and say which parts you could not verify.\n","# unity-debug — verify it yourself, and check the instrument first\n\nThe agent cannot see the Game view. **Never iterate via \"add a log → ask for a screenshot →\nguess\".** Unity will run itself, report to a log, and hand you PNGs you can read.\n\nThere is one rule above all the technique, and it is the one that costs the most when broken:\n\n> **A number is worthless until you know the run that produced it happened.**\n> Exit code 0 does not mean Unity started. A results file does not mean it is *this* run's results\n> file. A measurement does not mean the thing measured moved.\n\nA stale results XML reads \"6\u002F6 passed\" while Unity fails to start on every run. Start at\n`reference\u002Fharness-trust.md`; the guard is one line of `rm`.\n\n## Symptom → where to look\n\n| The report | Go to |\n|---|---|\n| \"exit 0 but no results file\", a run that did nothing, \"the tests are green but nothing was verified\" | `reference\u002Fharness-trust.md` |\n| \"which test failed\", `failed=0` that checked nothing | `reference\u002Ftest-verdicts.md` |\n| \"verify the fix works\" in the running game | *The four loops* |\n| \"the player won't move\", \"nothing happens when I press Play\" | `reference\u002Flog-triage.md`, then `reference\u002Feditor-control.md` |\n| \"the UI is shaking \u002F flickering\", anything temporal | `reference\u002Fmotion-and-timing.md`, `reference\u002Fvisual-checks.md` |\n| Green in the Editor, broken in a build | `reference\u002Fplayer-tests.md` |\n| Only breaks on the phone | skill `unity-device-testing` |\n| Anything else | *Load what the situation needs* |\n\n## The four loops\n\n**0 · Live-Editor loop** — fastest of all when the project has the Pipeline package: a running\nEditor answers `unity command` without recompiling or reloading the domain. Everything below\npays a cold start; this one does not. → `reference\u002Feditor-control.md`\n\n**1 · Log loop** — fastest when a human is at the keyboard. Instrument with a grep-able prefix, ask\nfor one Play, read Editor.log. → `reference\u002Flog-triage.md`\n\n**2 · CLI loop** — no human needed. `-batchmode` for compile and logic, ~20 s warm.\n→ `reference\u002Fcli-harness.md`\n\n**3 · Visual loop** — windowed `-runTests`, walk the whole flow, drop numbered PNGs, read them.\nCatches everything assertions cannot: overlap, clipping, contrast, wrong aspect.\n→ `reference\u002Fvisual-checks.md`\n\nBatchmode **cannot** screenshot (no end of frame). Windowed can, and IMGUI shows up in the capture.\nA live Editor can too, via `unity command screenshot` — which is loop 0's answer to loop 3.\n\nLoops 2 and 3 need not queue on one Editor: the lock is per project folder, so clone *lanes* run\nseveral Editors on one machine at once. → `reference\u002Fparallel-runs.md`\n---\n\n## Load what the situation needs\n\n| The situation | Read |\n|---|---|\n| About to trust a test result, or something reads as impossible | `reference\u002Fharness-trust.md` |\n| A run's verdict: which test failed, `failed=0` that checked nothing, state leaking between runs | `reference\u002Ftest-verdicts.md` |\n| Running Unity headless; tests not found; asmdef errors | `reference\u002Fcli-harness.md` |\n| Iterating more than twice; want to poke a live Editor; `unity command` won't connect; Safe Mode | `reference\u002Feditor-control.md` |\n| Need to SEE a screen; layout, contrast or cropping suspected | `reference\u002Fvisual-checks.md` |\n| The look changed and nobody meant it to; a screenshot diff against baselines, with an exit code | `reference\u002Fvisual-checks.md` (golden images) · `scripts\u002Fgolden_diff.py` |\n| The suite takes too long for one Editor; several agents want Unity at once; host and client in two Editors | `reference\u002Fparallel-runs.md` · `scripts\u002Flanes.sh` |\n| Other agents, Blender or a second project share the machine; a timing test red only sometimes; pipeline work that needs an Editor but not the game | `reference\u002Fparallel-runs.md` → \"The machine is shared\", \"A lab project\" |\n| Cyan materials or a frozen object on the first Play only; a capture that skews a timing number; a motion clip to review | `reference\u002Funity-gotchas.md` §22–23 · `reference\u002Fmotion-and-timing.md` |\n| A batchmode or EditMode tool samples a clip and every frame reads the bind pose | `reference\u002Funity-gotchas.md` §24 |\n| Briefing several agents: who owns lane 0, the Editor cap, push and hook rules | skill `unity-game-brief` → `templates\u002FAGENT_BRIEF.md` |\n| Green in the Editor, broken in a build: stripping, platform defines, init order — tests run inside a player | `reference\u002Fplayer-tests.md` |\n| \"It shakes \u002F flickers \u002F shimmers\"; anything temporal | `reference\u002Fmotion-and-timing.md` |\n| Runtime misbehaviour with a human pressing Play; device triage | `reference\u002Flog-triage.md` |\n| Phantom collisions, invisible objects, hitboxes, import weirdness | `reference\u002Funity-gotchas.md` |\n| The game cannot boot into the moment under test; nothing readable says what state it is in; a feel report with nothing to measure | skill `unity-play-harness` |\n| \"It is slow\", hitches, draw calls or GC — numbers you can compare across a change | skill `unity-profiling` |\n| A collision or trigger that never fires, tunnelling, a raycast that misses | skill `unity-physics-3d` · `unity-physics-2d` |\n| Post-processing set but not visible; reviewing a renderer feature | skill `unity-render-urp` |\n| A Scene-view or camera PNG for a before\u002Fafter comparison, outside a test run | skill `unity-urp-migration` → `resources\u002FEditor\u002FSceneCapture.cs` |\n| \"Find \u002F where is \u002F what references X\" — one query over project assets or the loaded scenes, rather than a script | skill `unity-search` |\n| Installing editors, licences, templates, MCP wiring, CI invocation | skill `unity-cli` |\n| An agent that will not move or path around something | skill `unity-navigation` |\n| Building the game's UI rather than debugging it | skill `unity-game-ui` |\n\n`resources\u002FDevDebug.cs` is a project-agnostic drop-in probe. Copy into `Assets\u002F`, attach,\n**delete when finished.** A permanent, contract-shaped probe that ships with the game and every run\ncan read is a different thing — that one is `unity-play-harness`.\n\n---\n\n## Discipline\n\n- **List, never recall.** Command names, template ids and package ids are defined by the Editor\n  and the registry, not by your memory of them. `unity command --format json`, `unity templates\n  list`, `Client.SearchAll()` — one call is cheaper than one wrong guess.\n- **Clone lanes run read-only work; anything that writes assets runs on lane 0.** Two Editors\n  importing into one `Assets\u002F` race on `.meta` files. → `reference\u002Fparallel-runs.md`.\n- **Delete the results file before every run.** A missing file is an obvious failure; a stale one\n  is a silent lie.\n- **Never pipe a test driver into `tail` or `head`.** The shell then reports the *pipe's* exit\n  status, so a driver that printed `exit=2 … failed=\"2\"` comes back to you as \"exited with code 0\".\n- **Read `inconclusive=` next to `failed=`.** `Assert.Inconclusive` leaves `failed=\"0\"`, so a whole\n  test class can skip itself — usually exactly when the assets it guards are missing — and the run\n  still reads green. → `reference\u002Ftest-verdicts.md`.\n- **Reset PlayerPrefs and persistent data in `[SetUp]`.** They survive between PlayMode runs, which\n  is how a suite passes on CI and fails on the developer's machine, and how \"the same test\" produces\n  two different screenshots.\n- **Log the state next to every screenshot** (`[SHOT] 04_countdown state=Countdown`) so a capture\n  that photographed the wrong moment cannot pass unnoticed.\n- **Print the numbers a test asserts on.** A green tick says a test passed; a logged\n  `world width=0.50 laneSpacing=1.30` says why, and keeps saying it after the next change.\n- **At most two Editors on the machine, whatever project they belong to**, and look at the load\n  (`uptime`, top of `ps`) before believing any millisecond. Another agent's Blender job made frame\n  times 2 to 5 times high and turned a smoke test red. `lanes.sh` queues at `MAX_UNITY`.\n- **Median and worst, never just worst** — one spike and a constant vibration are different faults.\n- **When a measurement contradicts the code, suspect the measurement.** Dump the pixels. Take a\n  whole-frame diff. The constants are rarely the liar.\n- **Re-run before calling a failure a regression.** Timing-sensitive tests exist, and a graphics\n  change can tip one over without touching gameplay. Say so plainly rather than inventing a cause.\n\n## Scope — what this skill does NOT do\n\n| Not here | Go to |\n|---|---|\n| Installing editors, licences, templates, CI invocation | `unity-cli` |\n| Building or signing an artifact | `unity-android-release` · `unity-web-release` |\n| A collision or trigger that never fires | `unity-physics-3d` · `unity-physics-2d` |\n| An agent that will not move | `unity-navigation` |\n| Post-processing that will not appear | `unity-render-urp` |\n| Designing the UI rather than verifying it | `unity-game-ui` |\n| Building the game so an agent can drive and read it: probes, named situations, journey tests | `unity-play-harness` |\n| Frame-time windows, profiler counters, a before\u002Fafter table | `unity-profiling` |\n| Deciding what to build first: the brief, the constraints, the first interaction | `unity-game-brief` |\n| \"Find \u002F where is \u002F what references X\" answered as a Unity Search query rather than a scripted audit | `unity-search` |\n| Verifying on a real phone rather than in the editor: adb \u002F devicectl drivers, a probe scene, a human in the loop | `unity-device-testing` |\n\n## Running PlayMode tests edits your project\n\nSide effects that all get committed if nobody looks:\n\n> **The test framework flips `runInBackground` to 1 in `ProjectSettings.asset` and does not put\n> it back.** A `git status` after a green test run is not clean, and the diff has nothing to do\n> with what you were testing.\n\n> **Restore that one LINE, never the whole file.** `git checkout -- ProjectSettings\u002FProjectSettings.asset`\n> is the obvious cleanup and it is destructive: it silently discards any Player Settings written\n> since the last commit — a setup step's target SDK level and app icons, say — which then have to\n> be regenerated. Restore surgically instead — and note that any *other* script running the suite\n> (a release build that tests before packaging) needs the same restore:\n>\n> ```bash\n> grep -q \"^  runInBackground: 1$\" ProjectSettings\u002FProjectSettings.asset && \\\n>   sed -i '' 's\u002F^  runInBackground: 1$\u002F  runInBackground: 0\u002F' ProjectSettings\u002FProjectSettings.asset\n> ```\n>\n> (BSD `sed` on macOS needs the empty `''` after `-i`; GNU `sed` takes `-i` alone.)\n\n> **A crashed run leaves files in the project.** `Assets\u002FInitTestScene\u003Cguid>.unity` plus its `.meta`\n> (the runner's temp scene) and a `mono_crash.mem.\u003Cpid>.\u003Cn>.blob` dump in the project root — both\n> swept up by the next `git add -A`. Ignore `Assets\u002FInitTestScene*` and `mono_crash.*`.\n\n> **Killing an Editor before a test run leaves `Temp\u002F` in a state that aborts the next one** with\n> *\"Scripts have compiler errors\"* and **no `error CS` line in the log** — the compiler never ran.\n> → `reference\u002Feditor-control.md`.\n\nSo the run protocol is: delete the results file, run, **then `git status`** — and revert what the\nharness changed before reporting anything as done.\n\n## Cleanup before handing back a \"clean\" build\n\n- Remove `[RUN]`\u002F`[DBG]` logs and per-frame dumps; remove `DevDebug.cs` and detach it.\n- Remove on-screen debug panels and debug-only serialized fields.\n- Keep the **fixes** found while debugging; delete only the **instrumentation**.\n- Leave the harness in a green, honestly-verified state — and say which parts you could not verify.\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-debug",0,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills","https:\u002F\u002Fgithub.com\u002FtipoLi5890","https:\u002F\u002Ftipoli5890.github.io\u002F","2026-11-10 09:16:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tipoLi5890\u002Funity-dev-skills --skill unity-debug",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-debug",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,94,98,104,108],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fcli-harness.md","REFERENCE","参考文档",10612,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fcli-harness.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Feditor-control.md",12808,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Feditor-control.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fharness-trust.md",9704,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fharness-trust.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Flog-triage.md",3796,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Flog-triage.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"reference\u002Fmotion-and-timing.md",6857,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fmotion-and-timing.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"reference\u002Fparallel-runs.md",22430,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fparallel-runs.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"reference\u002Fplayer-tests.md",10530,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fplayer-tests.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"reference\u002Ftest-verdicts.md",12191,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Ftest-verdicts.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"reference\u002Funity-gotchas.md",10913,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Funity-gotchas.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"reference\u002Fvisual-checks.md",19542,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Freference\u002Fvisual-checks.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"resources\u002FDevDebug.cs","OTHER","其他",2977,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Fresources\u002FDevDebug.cs",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"resources\u002FLaneDataPath.cs",2987,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Fresources\u002FLaneDataPath.cs",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fgolden_diff.py","SCRIPT","脚本",23511,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Fscripts\u002Fgolden_diff.py",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Flanes.sh",22090,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Fscripts\u002Flanes.sh",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fmerge_results.py",14265,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-debug\u002Fscripts\u002Fmerge_results.py",[113,120,127,134,141,148],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7CMNYXQNW14ST64EYEEZ5V5","unity-web-release","Ship a WebGL\u002FWebGPU build: shrink the download, Brotli server headers, Safari and iPhone memory.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-web-release\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7CMNTHD1EA70CCJ2F9FN3HT","unity-vivox","Vivox voice and text chat: channels, positional voice, mute and push-to-talk, mic permission.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-vivox\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7CMNPHPRQZ7K1FES2953DRQ","unity-urp-migration","Migrate a Built-in project to URP, or fix a half-moved one: pink materials, PPv2, old shaders.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-urp-migration\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7CMNJ756DK4V0D50HMAZYQW","unity-ui-ugui","Canvas UI (uGUI): CanvasScaler, RectTransform anchors, Layout Groups, ScrollView, UI built from C#.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-ugui\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7CMNDESZN79EK5FRDXCA2WA","unity-ui-toolkit","UI Toolkit (UXML, USS, UIDocument): flex layout, binding, custom elements, editor windows.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-toolkit\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":19},"01M7CMN8GBV07K0YCY07BJ6A1W","unity-ugs","Unity Gaming Services API: which package, init and sign-in order, Cloud Save, Cloud Code, Remote Config.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ugs\u002FSKILL.md",[],[]]