Update to Unity Essentials

{
  "description": "Validate that a Unity project or completed change is ready to compile, test, build, and hand off. Use when the user asks to verify a feature, confirm build readiness, check compilation, run tests, validate scenes and prefabs, inspect Console output, confirm target-platform compatibility, prepare a release candidate, or determine whether Unity work is truly complete. Establish a baseline, run the strongest available validation, distinguish pre-existing failures from introduced regressions, and report exact evidence without overstating confidence.",
  "included_files": [
    {
      "relative_path": "FILE-INVENTORY.md",
      "size_in_bytes": 1463
    },
    {
      "relative_path": "README.md",
      "size_in_bytes": 857
    },
    {
      "relative_path": "checklists/builds-and-artifacts.md",
      "size_in_bytes": 533
    },
    {
      "relative_path": "checklists/ci-and-reproducibility.md",
      "size_in_bytes": 379
    },
    {
      "relative_path": "checklists/compilation-and-console.md",
      "size_in_bytes": 561
    },
    {
      "relative_path": "checklists/multiplayer.md",
      "size_in_bytes": 452
    },
    {
      "relative_path": "checklists/packages-and-assemblies.md",
      "size_in_bytes": 431
    },
    {
      "relative_path": "checklists/performance-budgets.md",
      "size_in_bytes": 491
    },
    {
      "relative_path": "checklists/prefabs-and-serialization.md",
      "size_in_bytes": 480
    },
    {
      "relative_path": "checklists/release-candidate.md",
      "size_in_bytes": 489
    },
    {
      "relative_path": "checklists/rendering-shaders-vfx.md",
      "size_in_bytes": 361
    },
    {
      "relative_path": "checklists/runtime-smoke-tests.md",
      "size_in_bytes": 431
    },
    {
      "relative_path": "checklists/save-and-migration.md",
      "size_in_bytes": 352
    },
    {
      "relative_path": "checklists/scenes-and-build-settings.md",
      "size_in_bytes": 482
    },
    {
      "relative_path": "checklists/tests.md",
      "size_in_bytes": 519
    },
    {
      "relative_path": "checklists/ui-localization-input.md",
      "size_in_bytes": 434
    },
    {
      "relative_path": "checklists/xr-and-devices.md",
      "size_in_bytes": 347
    },
    {
      "relative_path": "foundations/baseline-and-regression.md",
      "size_in_bytes": 1033
    },
    {
      "relative_path": "foundations/evidence-levels.md",
      "size_in_bytes": 1475
    },
    {
      "relative_path": "foundations/status-and-reporting.md",
      "size_in_bytes": 1081
    },
    {
      "relative_path": "foundations/validation-safety.md",
      "size_in_bytes": 1091
    },
    {
      "relative_path": "frameworks/networking/fishnet.md",
      "size_in_bytes": 194
    },
    {
      "relative_path": "frameworks/networking/fusion.md",
      "size_in_bytes": 382
    },
    {
      "relative_path": "frameworks/networking/mirror.md",
      "size_in_bytes": 223
    },
    {
      "relative_path": "frameworks/networking/netcode-for-gameobjects.md",
      "size_in_bytes": 320
    },
    {
      "relative_path": "frameworks/platforms/android.md",
      "size_in_bytes": 319
    },
    {
      "relative_path": "frameworks/platforms/dedicated-server.md",
      "size_in_bytes": 334
    },
    {
      "relative_path": "frameworks/platforms/ios.md",
      "size_in_bytes": 253
    },
    {
      "relative_path": "frameworks/platforms/linux.md",
      "size_in_bytes": 217
    },
    {
      "relative_path": "frameworks/platforms/macos.md",
      "size_in_bytes": 244
    },
    {
      "relative_path": "frameworks/platforms/webgl.md",
      "size_in_bytes": 254
    },
    {
      "relative_path": "frameworks/platforms/windows.md",
      "size_in_bytes": 270
    },
    {
      "relative_path": "frameworks/rendering/hdrp.md",
      "size_in_bytes": 226
    },
    {
      "relative_path": "frameworks/rendering/urp.md",
      "size_in_bytes": 266
    },
    {
      "relative_path": "references/acceptance-matrix-template.md",
      "size_in_bytes": 187
    },
    {
      "relative_path": "references/capability-requirements.md",
      "size_in_bytes": 932
    },
    {
      "relative_path": "references/status-summary-template.md",
      "size_in_bytes": 206
    },
    {
      "relative_path": "references/validation-plan-template.md",
      "size_in_bytes": 508
    },
    {
      "relative_path": "references/validation-report-template.md",
      "size_in_bytes": 542
    }
  ],
  "name": "unity-build-validation",
  "skill_md_contents": "---\nname: unity-build-validation\ndescription: Validate that a Unity project or completed change is ready to compile, test, build, and hand off. Use when the user asks to verify a feature, confirm build readiness, check compilation, run tests, validate scenes and prefabs, inspect Console output, confirm target-platform compatibility, prepare a release candidate, or determine whether Unity work is truly complete. Establish a baseline, run the strongest available validation, distinguish pre-existing failures from introduced regressions, and report exact evidence without overstating confidence.\n---\n\n# Unity Build Validation\n\nValidate Unity work using progressively stronger evidence.\n\nThis skill is the final verification layer for feature implementation, bug\nfixes, health-check remediation, milestones, and release preparation.\n\nCompilation is necessary but not sufficient.\n\nA change is not fully validated merely because C# compiles.\n\n## Surface Limits\n\nIf the current surface is Chat mode without an attached workspace, repository files, build logs, or local filesystem access, do not claim build readiness or validation. Explain that Unity Essentials can help interpret pasted build output, but real build validation requires Codex with the Unity project folder open, a connected Unity Editor, CI output, or supplied build logs.\n\nIf Codex has a workspace or local files available, validate with the strongest available evidence and clearly state any missing Unity Editor, test, platform, or device coverage.\n\n## Primary outcome\n\nProduce an exact validation result that answers:\n\n- Did Unity compile?\n- Were new Console errors introduced?\n- Which tests ran and what passed?\n- Are required scenes configured?\n- Are prefabs and serialized references valid?\n- Does the target build succeed?\n- Was runtime behavior exercised?\n- Were platform-specific checks completed?\n- What remains unverified?\n- Is the result ready, conditionally ready, blocked, or not validated?\n\n## Relationship with other skills\n\nThis skill may be used after:\n\n- `unity-feature-implementation`\n- `unity-bug-investigation`\n- `unity-project-health-check`\n- manual project changes\n- package changes\n- scene or prefab changes\n- release preparation\n\nUse project context from:\n\n- `unity-project-onboarding`\n- `Docs/AI/UnityProjectContext.md`\n- repository instructions\n- build documentation\n- CI workflows\n\nDo not repeat broad architecture analysis unless it is required to understand a\nvalidation failure.\n\n## Default behavior\n\nValidation may execute tests, enter Play Mode, or trigger builds when those\noperations are appropriate and available.\n\nDo not modify production code or project assets merely to make validation pass.\n\nDo not:\n\n- disable failing tests\n- clear the Console before recording the baseline\n- suppress warnings without understanding them\n- change build settings casually\n- update packages\n- delete user data\n- rewrite scenes or prefabs\n- mark a build ready based only on static inspection\n\n## Knowledge routing\n\nThe skill contains:\n\n- `foundations/`: validation principles\n- `checklists/`: validation domains\n- `frameworks/`: framework and platform-specific rules\n- `references/`: plans, reports, status definitions, and capabilities\n\n### Mandatory foundations\n\nAlways read:\n\n- `foundations/evidence-levels.md`\n- `foundations/baseline-and-regression.md`\n- `foundations/validation-safety.md`\n- `foundations/status-and-reporting.md`\n\n### Checklist routing\n\n| Validation domain | File |\n|---|---|\n| Compilation and Console | `checklists/compilation-and-console.md` |\n| EditMode and PlayMode tests | `checklists/tests.md` |\n| Scenes and Build Settings | `checklists/scenes-and-build-settings.md` |\n| Prefabs and serialization | `checklists/prefabs-and-serialization.md` |\n| Runtime smoke testing | `checklists/runtime-smoke-tests.md` |\n| Builds and artifacts | `checklists/builds-and-artifacts.md` |\n| Packages and assemblies | `checklists/packages-and-assemblies.md` |\n| Performance budgets | `checklists/performance-budgets.md` |\n| Multiplayer validation | `checklists/multiplayer.md` |\n| Save and migration validation | `checklists/save-and-migration.md` |\n| UI, localization, and input | `checklists/ui-localization-input.md` |\n| Rendering, shaders, and VFX | `checklists/rendering-shaders-vfx.md` |\n| XR and devices | `checklists/xr-and-devices.md` |\n| CI and reproducibility | `checklists/ci-and-reproducibility.md` |\n| Release candidate validation | `checklists/release-candidate.md` |\n\n### Framework routing\n\nRead framework guidance only when active use is confirmed.\n\n| Framework or platform | File |\n|---|---|\n| Photon Fusion | `frameworks/networking/fusion.md` |\n| Netcode for GameObjects | `frameworks/networking/netcode-for-gameobjects.md` |\n| Mirror | `frameworks/networking/mirror.md` |\n| FishNet | `frameworks/networking/fishnet.md` |\n| URP | `frameworks/rendering/urp.md` |\n| HDRP | `frameworks/rendering/hdrp.md` |\n| Windows | `frameworks/platforms/windows.md` |\n| Android | `frameworks/platforms/android.md` |\n| iOS | `frameworks/platforms/ios.md` |\n| WebGL | `frameworks/platforms/webgl.md` |\n| Linux | `frameworks/platforms/linux.md` |\n| macOS | `frameworks/platforms/macos.md` |\n| Dedicated server | `frameworks/platforms/dedicated-server.md` |\n\n## Validation modes\n\n### Change validation\n\nUse after a specific implementation or bug fix.\n\nFocus on:\n\n- changed assemblies\n- affected scenes and prefabs\n- relevant tests\n- original behavior or reproduction\n- regression surface\n\n### Project validation\n\nUse for a general readiness check.\n\nFocus on:\n\n- project compilation\n- Console baseline\n- test suites\n- build scenes\n- target build\n- critical assets\n\n### Release candidate validation\n\nUse before publishing or handing off a build.\n\nInclude:\n\n- clean build\n- target platform\n- release configuration\n- smoke tests\n- save compatibility\n- networking\n- performance budgets\n- version and artifact metadata\n- reproducibility\n\n### CI validation\n\nUse when validating automated commands or pipelines.\n\nConfirm:\n\n- command reproducibility\n- exit codes\n- test result artifacts\n- build artifacts\n- environment requirements\n- secret handling\n- failure visibility\n\n## Core principles\n\n1. Record the baseline before running validation.\n2. Distinguish pre-existing failures from regressions.\n3. Validate the changed surface first.\n4. Progress from cheap to strong evidence.\n5. Use the actual target platform when required.\n6. Report exact commands, tests, scenes, and artifacts.\n7. Do not claim runtime behavior from compilation.\n8. Do not claim multiplayer correctness from one instance.\n9. Do not claim visual correctness without visual inspection.\n10. Do not claim performance compliance without measurement.\n11. Preserve failing evidence.\n12. Report blocked and unverified areas explicitly.\n\n## Phase 1: Define validation contract\n\nDetermine:\n\n- what change or project state is being validated\n- acceptance criteria\n- target platform\n- build configuration\n- scenes or features involved\n- required test suites\n- required runtime scenarios\n- performance or memory budgets\n- multiplayer topology\n- device or XR requirements\n- artifact expectations\n- release stage\n\nIf no explicit criteria exist, infer the smallest meaningful validation set from\nthe change and project context.\n\n## Phase 2: Establish baseline\n\nBefore changing state:\n\n- record Git commit and working tree status\n- inspect changed files\n- read current Console messages\n- record known failing tests\n- record Unity and package versions\n- record active target platform\n- record Build Settings scenes\n- identify existing build and CI commands\n- identify required environment variables without exposing their values\n\nDo not clear the Console until baseline evidence is preserved.\n\n## Phase 3: Select validation level\n\nUse `foundations/evidence-levels.md`.\n\nChoose the strongest practical level required by the change.\n\nExamples:\n\n- plain C# calculation: compile + EditMode tests\n- MonoBehaviour lifecycle: compile + PlayMode or runtime\n- prefab integration: compile + serialized reference inspection + runtime\n- multiplayer: multi-peer validation\n- shader: shader compilation + visual validation\n- platform API: target build + target device\n- save migration: old save + new save + reload\n- performance fix: before/after measurement\n\n## Phase 4: Validate compilation and Console\n\nUse `checklists/compilation-and-console.md`.\n\nWhen Unity is connected:\n\n1. Confirm active project.\n2. Allow import and compilation to finish.\n3. Read Console errors and warnings.\n4. Separate pre-existing messages from new messages.\n5. Identify assembly or package failures.\n6. Do not clear messages needed as evidence.\n\nWhen Unity is unavailable, use the strongest fallback:\n\n- CI compilation\n- generated solution compilation\n- static analysis\n- assembly-specific commands\n\nReport that Unity Editor compilation was not confirmed.\n\n## Phase 5: Run tests\n\nUse `checklists/tests.md`.\n\nPrefer targeted tests first, then broader suites.\n\nRecord:\n\n- test category\n- test names or filters\n- passed\n- failed\n- skipped\n- duration when useful\n- pre-existing versus new failures\n- test result artifact paths\n\nDo not disable or ignore failures to obtain a green result.\n\n## Phase 6: Validate scenes and serialized assets\n\nUse:\n\n- `checklists/scenes-and-build-settings.md`\n- `checklists/prefabs-and-serialization.md`\n\nConfirm:\n\n- required scenes exist\n- enabled scenes are correct\n- startup flow is valid\n- no required references are missing\n- prefab variants remain valid\n- ScriptableObject defaults are safe\n- new `.meta` files exist\n- no unintended broad serialization changes occurred\n\nDo not open and save scenes merely to inspect them.\n\n## Phase 7: Runtime smoke test\n\nUse `checklists/runtime-smoke-tests.md`.\n\nExercise the smallest runtime scenario that proves the changed behavior.\n\nRecord:\n\n- scene\n- object or feature\n- steps\n- expected result\n- observed result\n- Console state\n- repetitions\n- cleanup or reload behavior\n\nDo not say “tested in Play Mode” without stating what was exercised.\n\n## Phase 8: Build target artifacts\n\nUse `checklists/builds-and-artifacts.md`.\n\nWhen a target build is required:\n\n- confirm platform\n- confirm configuration\n- confirm scenes\n- confirm output path\n- record command or build method\n- record duration when useful\n- inspect warnings and failures\n- verify artifact existence\n- verify artifact metadata\n- launch or install when appropriate\n\nA successful Editor compile does not prove a player build succeeds.\n\n## Phase 9: Run framework and platform checks\n\nLoad the relevant framework and platform guides.\n\nExamples:\n\n- networking topology\n- dedicated-server symbols\n- WebGL threading restrictions\n- Android permissions and ABI\n- iOS signing and IL2CPP\n- Windows architecture\n- shader and graphics API support\n\nDo not mark platform validation complete without platform-relevant evidence.\n\n## Phase 10: Validate acceptance criteria\n\nUse a traceable matrix:\n\n- criterion\n- evidence\n- status\n- limitation\n\nEvery acceptance criterion must be:\n\n- Passed\n- Failed\n- Blocked\n- Not run\n- Not applicable\n\nDo not omit failed criteria from the final report.\n\n## Phase 11: Review working tree and artifacts\n\nBefore completion:\n\n- inspect final diff\n- identify generated files\n- identify unintended changes\n- ensure temporary diagnostics are removed\n- ensure test artifacts are stored appropriately\n- ensure build artifacts are outside source directories unless expected\n- ensure secrets were not written to logs or reports\n- record artifact paths\n\n## Phase 12: Assign validation status\n\nUse `foundations/status-and-reporting.md`.\n\nAllowed overall statuses:\n\n- Ready\n- Ready with limitations\n- Blocked\n- Failed\n- Not validated\n\nDo not use Ready when a required criterion was not run.\n\n## Prohibited behavior\n\nDo not:\n\n- declare success from compilation alone\n- hide failing tests\n- clear evidence before recording it\n- change code to silence tests without understanding the failure\n- remove scenes from Build Settings to make a build pass\n- disable stripping, signing, or platform constraints casually\n- update dependencies during validation\n- replace test data\n- skip the original bug reproduction\n- claim two-peer validation from one process\n- claim performance improvement without equivalent measurements\n- claim visual quality from code inspection\n- expose signing credentials or tokens\n\n## Definition of done\n\nValidation is complete when:\n\n- scope and acceptance criteria are explicit\n- baseline is recorded\n- required validation levels are selected\n- compilation status is known\n- Console regressions are classified\n- required tests were run\n- scenes and serialized assets were checked\n- runtime behavior was exercised when required\n- target build was produced when required\n- framework and platform checks were applied\n- acceptance criteria have statuses\n- final diff and artifacts were reviewed\n- overall status is assigned honestly\n- limitations are explicit\n\n## Final response\n\nReturn:\n\n### Status\n\nReady / Ready with limitations / Blocked / Failed / Not validated\n\n### Validation summary\n\nSummarize the strongest evidence.\n\n### Acceptance criteria\n\nList each criterion and status.\n\n### Tests and builds\n\nInclude exact suites, platforms, and artifact paths.\n\n### Regressions\n\nState new, pre-existing, and unresolved failures.\n\n### Limitations\n\nState what was not validated and why.\n\n### Recommended next action\n\nInclude only the most important action required to reach Ready.\n"
}