t1k:unity:web:audit
| Field | Value |
|---|---|
| Module | web |
| Version | 2.32.3 |
| Effort | high |
| Tools | — |
Keywords: audit, browser, compatibility, estimate, readiness, wasm, web, webassembly, webgl
How to invoke
Section titled “How to invoke”/t1k:unity:web:auditAudit Unity Web Readiness
Section titled “Audit Unity Web Readiness”Produce an evidence-backed compatibility report before conversion or optimization. Remain read-only.
Inputs
Section titled “Inputs”- Unity project root. Confirm
Assets/andProjectSettings/exist. - Target:
desktop,mobile, orboth(default). - Optional
--estimaterequest.
Workflow
Section titled “Workflow”-
Run the deterministic scanner:
Terminal window bun .claude/skills/t1k-unity-web-audit/scripts/scan-web-compat.cjs <project-root> --format jsonWhen running from this source repo, use the module-local path under
.claude/modules/web/skills/t1k-unity-web-audit/.The target affects the manual browser/device checklist and estimate, not the static C# scan. Treat incomplete scanner coverage as
buildable-with-work, neverready-to-profile. -
Inspect systems the scanner cannot prove:
- Package vendor Web support and native plugin replacements.
- Ads, IAP, authentication, analytics, notifications, deep links, and privacy SDKs.
- Browser input, resize/orientation/fullscreen, iframe embedding, and mobile safe areas.
- Audio unlock after user interaction and microphone requirements.
- Persistence semantics, IndexedDB availability, quota, and private browsing.
- Fetch/CORS/WebSocket requirements and server ownership.
- URP shaders, compute/VFX usage, memory assumptions, and representative device budgets.
- Reflection/serialization preservation and required
link.xmlentries.
-
Classify every finding with file/line evidence when available:
blocker: cannot produce a representative Web build without a design or replacement.warning: build may work, but behavior or portability is uncertain.info: known platform seam requiring explicit validation.
-
Assign the overall status:
blocked: at least one unresolved blocker.buildable-with-work: no blockers, but warnings remain.ready-to-profile: no blockers or warnings; browser validation is still required.
-
If requested, estimate by subsystem rather than one opaque total. State assumptions and confidence.
Executed by
Section titled “Executed by”The read-only enumeration and classification work delegates to cheap-tier agents; only the
judgment of what a finding means for the port stays on a reasoning tier (routing SSOT:
rules/orchestration-rules.md § “Task-Type → Agent Routing”):
| Step | Agent |
|---|---|
| Run the static scanner and enumerate which C# assets use Web-incompatible APIs | t1k-list-classifier — categories (blocker/warning/info) are supplied by the skill’s rubric |
| Read a package’s vendor docs or manifest to quote its stated Web support and native-plugin replacements | t1k-fact-fetcher |
Label each finding blocker / warning / info with its evidence line | t1k-list-classifier |
| Aggregate scan + classification into the finding table and matrix | t1k-metrics-reporter |
Decide what the unresolved blockers mean for the port and set the overall status (blocked / buildable-with-work / ready-to-profile) | reasoning tier — judging port impact, not applying a rubric |
| Estimate migration effort by subsystem | reasoning tier — an estimate is a judgment, not a measurement |
The scanner output plus the skill’s severity rubric fully specify the classification step — no finding requires interpretation to be labeled. The moment the question turns from which category does this finding carry? to does this blocker actually block this port?, it has changed tier. This command is read-only start to finish, so no executor step holds write tools
Required output
Section titled “Required output”Include:
- Status and target.
- Finding table: ID, severity, category, evidence, impact, remediation, owner.
- Package/platform feature matrix.
- Unsupported-feature register.
- Estimate by subsystem with assumptions.
- Recommended next command:
- compatibility blockers →
/t1k:unity:web:convert - successful representative build →
/t1k:unity:web:optimize
- compatibility blockers →
Never claim Editor Play Mode proves browser compatibility. Never edit project files from this command.
Read references/compatibility-checklist.md when validating browser behavior, packages, or findings not covered by the scanner.