immersive-web-sdk

Test XR session lifecycle and mode transitions. Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues.

Test Havok physics system (gravity, rigid bodies, static vs dynamic) against the physics example using the iwsdk CLI.

Test environment system (authored DomeGradient and IBLGradient, component schemas) against the poke example using the iwsdk CLI.

Test UIKitML asset and ScreenSpace UI behavior against the poke example using the iwsdk CLI.

Test XR interactions (ray, poke/touch, dual-mode, audio, UI panel) against the poke example using the iwsdk CLI.

Test locomotion system (slide, snap turn, teleport, jump) against the locomotion example using the iwsdk CLI.

Test level system (LevelRoot, LevelTag, authored environment, scene hierarchy) against the poke example using the iwsdk CLI.

Test grab system (distance grab, one-hand grab, two-hand grab) against the grab example using the iwsdk CLI.

Create, place, preview, debug, and connect manifest-backed IWSDK UIKitML assets. Use for spatial panels, browser HUDs, UIKitML layout, fonts, editor previews, or runtime element behavior.

Test ECS core functionality (system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots) against the poke example using the iwsdk CLI.

Parallel test orchestrator. Runs all 9 test suites concurrently via Task sub-agents and the iwsdk CLI. Handles build, example setup, dev servers, agent launch, polling, retries, and result aggregation.

Test audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.

Find and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.

IWSDK experience pipeline and planning guide. Use when building a new IWSDK app/game end-to-end, planning new IWSDK features, designing systems/components, reviewing IWSDK code architecture, or when the user asks about IWSDK patterns, ECS design, signals, or reactive programming. Runs a phased ideation → design → grounding → architecture → build → verify → ship pipeline, orchestrating sub-agents per phase where the harness supports them.