xr-mode-test
Skill350 starsChanged 25 days agoMITView on GitHub
Test XR session lifecycle and mode transitions. Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues.
In this repository13 other files it gives its agents.
- click-targetSkill
- iwsdk-devSkill
- iwsdk-ui-panelSkill
- test-allSkill
- test-audioSkill
- test-ecs-coreSkill
- test-environmentSkill
- test-grabSkill
- test-interactionsSkill
- test-levelSkill
- test-locomotionSkill
- test-physicsSkill
- test-uiSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Test the XR session lifecycle by entering and exiting XR mode, verifying state transitions at each step.
- Very specific: line 15
Use mcp__iwsdk-runtime__xr_get_session_status to confirm starting state:
- Very specific: line 22
Use mcp__iwsdk-runtime__xr_accept_session to enter XR.
- Very specific: line 26
Use mcp__iwsdk-runtime__xr_get_session_status to confirm:
- Very specific: line 33
Use mcp__iwsdk-runtime__xr_get_device_state to check:
- Very specific: line 40
Use mcp__iwsdk-runtime__xr_end_session to leave XR.
- Very specific: line 51
Use mcp__iwsdk-runtime__browser_get_console_logs to verify:
- Very specific: line 58
If $ARGUMENTS is provided, use it as a log pattern filter for step 7.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
XR Mode Toggle Test
Test the XR session lifecycle by entering and exiting XR mode, verifying state transitions at each step.
Test Flow
1. Check Initial State
Use mcp__iwsdk-runtime__xr_get_session_status to confirm starting state:
- In 2D mode: no active session
- Already in XR: note current state before proceeding
2. Enter XR Mode
Use mcp__iwsdk-runtime__xr_accept_session to enter XR.
3. Verify XR Session Active
Use mcp__iwsdk-runtime__xr_get_session_status to confirm:
- Session is active
visibilityStateis"visible"
4. Optional: Verify Input Devices
Use mcp__iwsdk-runtime__xr_get_device_state to check:
- Controllers are connected
- Headset position is valid
5. Exit XR Mode
Use mcp__iwsdk-runtime__xr_end_session to leave XR.
6. Verify Session Ended
Use mcp__iwsdk-runtime__xr_get_session_status to confirm:
- No active session
- Back to 2D mode
7. Check Application State
Use mcp__iwsdk-runtime__browser_get_console_logs to verify:
- Any mode-switch logs fired correctly
- Application state reset as expected (if applicable)
Arguments
If $ARGUMENTS is provided, use it as a log pattern filter for step 7.
Example: /xr-mode-test "MODE|RESET" will filter logs for "MODE" or "RESET" patterns.
Expected Results
Report:
- Whether each step passed or failed
- Any unexpected state or errors
- Time taken for session transitions
- Relevant log messages from the application
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.