PlayCanvas WebXR sessions
Plans entry into and exit from XR while retaining the normal game controls. It handles capability checks, tracking loss and rejected sessions, naming where real-device verification is still needed.
playcanvas-webxr-sessions
See how it helpsWhen is it useful?
Use when adding headset sessions to an existing browser game.
What does it help you do?
- Checks secure context and actual session or device capabilities.
- Maps XR input to existing actions and owns session resources.
- Handles rejected entry and restores normal view after exit.
Try asking this
Add an AR inspection mode to our treasure-hunt game. Try unsupported hardware, cancelled entry and lost tracking before returning to the normal camera. The interface must explain unavailable features and restore standard input; record which transitions were tested on an actual device.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
PlayCanvas — webxr sessions
Use when implementing requested PlayCanvas WebXR sessions, tracked input or XR presentation.
Version and project gate
Inspect Engine version, Engine-only versus hosted Editor workflow, ESM versus classic scripts, build/export process, asset IDs and tags, render backend, script attributes and target browser requirements. Do not assume a paid Editor service is required for Engine-only work. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Check the installed XR API, secure context and session/device capabilities. Define entry, rejection, tracking loss and exit behavior. Map XR input into the same game commands as standard input and clean session-owned resources. Use measured device behavior for comfort decisions.
Deliver
An XR lifecycle and interaction contract with explicit device checks still needed. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A browser emulator cannot establish headset tracking or user comfort.
Acceptance scenario
Cancel entry, lose a controller, leave XR and continue in the standard view without duplicated input or render ownership. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Cyra. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md