iwsdk-depth-occlusion
Skill1 starsChanged 32 days agoMITView on GitHub
Add or repair IWSDK WebXR depth sensing and real-world occlusion in AR. Use for DepthSensingSystem, DepthOccludable, occlusion modes, or passthrough depth troubleshooting.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cf-cliSkill
- durable-objectsSkill
- game-gdd-authorSkill
- game-playtestSkill
- pmndrs-handleSkill
- pmndrs-pointer-eventsSkill
- pmndrs-uikitSkill
- prototype-fastSkill
- pwa-offlineSkill
- review-game-trailerSkill
- scenario-blender-expertSkill
- scenario-blender-retopologySkill
- scenario-blender-uv-bakingSkill
- threejs-perf-loadingSkill
- webapp-testingSkill
- workers-best-practicesSkill
- wranglerSkill
- xr-perceptual-constraints-displays-and-trackingSkill
- xr-platforms-audio-and-comfortSkill
- xr-referenceSkill
- xr-rendering-input-and-spatial-understandingSkill
- xr-ux-design-and-performance-budgetingSkill
- horizon-launch-roadmapSkill
- horizon-store-listing-assetsSkill
- horizon-web-store-publishSkill
- horizon-web-vrc-checklistSkill
- iwsdk-asset-pipelineSkill
- iwsdk-dev-workflowSkill
- iwsdk-performanceSkill
- iwsdk-project-setupSkill
- iwsdk-quest-device-testingSkill
- iwsdk-testingSkill
- iwsdk-vr-glassesSkill
- quest-browser-webxrSkill
- iwsdk-build-modelSkill
- iwsdk-compose-sceneSkill
- iwsdk-debugSkill
- iwsdk-devSkill
- iwsdk-grabSkill
- iwsdk-hostingSkill
- iwsdk-migrate-0-5Skill
- iwsdk-native-xr-testSkill
- iwsdk-physicsSkill
- iwsdk-pwa-packagingSkill
- iwsdk-raySkill
- iwsdk-uiSkill
- hz-immersive-designerSkill
- hz-iwsdk-webxrSkill
- hz-new-project-creationSkill
- hz-perfetto-debugSkill
- hz-quest-verify-firstSkill
- hz-simpleperf-debugSkill
- hz-store-pwaSkill
- hz-store-submitSkill
- hz-vr-debugSkill
- metavr-cliSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Keep world.xr.mode as "ar".
- Very specific: line 32
Import and register DepthSensingSystem exactly once after World.create:
- Very specific: line 46
Add DepthOccludable only to the requested scene nodes.
- Distinctive: line 52
Leave a deliberate non-occludable reference object when comparison is part of the request.
- Distinctive: line 57
Run the production build once, start the AR app once, enter XR, and query the named entities and registered systems.
- Distinctive: line 65
Use one XR entry, one bounded entity/system query set, and one console check.
- Very specific: line 70
Use the CLI action names below.
- Very specific: line 83
Use npx @iwsdk/cli browser screenshot --output-file <path> for file evidence.
- Distinctive: line 86
Do not inspect framework source when the build, registered-system query, entity components, and console warnings already establish the …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
IWSDK Depth Occlusion
Depth occlusion has three independent requirements: the AR session requests
depth, one depth system is registered, and only intended virtual entities carry
DepthOccludable.
Implement
- Inspect
iwsdk.config.json,src/index.ts, and the active scene in one bounded pass, then make the complete config/system/scene edit before starting the dev server. The contracts below are sufficient for the normal path: do not call scene capabilities, CLI--help, inspectnode_modules, or read generated declarations unless a concrete build/runtime error remains. Keep
world.xr.modeas"ar". Underworld.xr.features, request:"depthSensing": { "required": true, "usage": "gpu-optimized", "format": "float32" }Preserve other required AR features. Use the living-room emulator (or the environment requested by the task) so runtime depth exists.
Import and register
DepthSensingSystemexactly once afterWorld.create:world.registerSystem(DepthSensingSystem, { configData: { enableDepthTexture: true, enableOcclusion: true, useFloat32: true, blurRadius: 20, }, });DepthOccludableis built in. Do not callregisterComponentfor it.- Add
DepthOccludableonly to the requested scene nodes. These scene payloads are exact:{}means soft occlusion and{ "mode": "HardOcclusion" }means sharp low-cost occlusion. Use"MinMaxSoftOcclusion"only when the task needs the higher-quality path. Write the literal scene value directly; do not load the scene-composer format reference, importOcclusionShadersMode, or inspect its declaration to reconfirm it. - Leave a deliberate non-occludable reference object when comparison is part of the request. Do not mark UI or guidance surfaces occludable by default.
Verify
Run the production build once, start the AR app once, enter XR, and query the named entities and registered systems. Check the console for missing depth-sensing warnings. Capture one runtime screenshot in the configured room; source inspection or an authored scene render alone cannot prove passthrough occlusion. Make one focused correction if the measured runtime disagrees, then stop. Do not repeatedly restart the emulator or tune blur from screenshots when the session never exposed depth data.
Use one XR entry, one bounded entity/system query set, and one console check. Save the final live screenshot but do not read it back when those runtime checks already prove that depth was requested, the system is live, and the intended entities carry the correct occlusion modes.
Use the CLI action names below; do not substitute MCP method names or probe
--help first:
npx @iwsdk/cli xr enter
npx @iwsdk/cli xr status
npx @iwsdk/cli ecs find --input-json '{"namePattern":"<requested node regex>"}'
npx @iwsdk/cli ecs query --input-json '{"entityIndex":<index from find>}'
npx @iwsdk/cli ecs systems
npx @iwsdk/cli browser logs --count 80
npx @iwsdk/cli browser screenshot --output-file artifacts/<name>.pngUse npx @iwsdk/cli browser screenshot --output-file <path> for file evidence. Do
not alter the project camera or render extra authored angles to manufacture an
occlusion view; stage the requested nodes once, then judge the live AR capture.
Do not inspect framework source when the build, registered-system query, entity
components, and console warnings already establish the failing layer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

