Automated summary
This skill provides VR/AR development principles covering platform selection, motion-sickness prevention, per-headset performance budgets, and spatial design conventions.
Strengths
- Clear reference tables for VR (Quest, PCVR, PSVR, WebXR) and AR (ARKit, ARCore, HoloLens) platforms
- Concrete FPS and resolution targets per device, with an explicit frame budget (11.11 ms at 90 FPS)
- Actionable list of motion-sickness causes paired with comfort settings
- Concrete anti-patterns (player-driven camera, readable text size, 1 unit = 1 meter scale)
Limitations
- Mostly reference tables, with no code samples or implementation walkthroughs
- Hardware figures (Quest 2/3, PSVR2) will age as new headsets ship
- Does not cover rendering, shaders, GPU optimization, or asset pipelines
Use it to frame comfort, performance, and interaction decisions when starting or reviewing a VR/AR project.
Avoid it if you need ready-to-run code, engine-specific tutorials (Unity/Unreal), or advanced rendering optimization techniques.
Security analysis
SafeThis is a purely informational reference document about VR/AR development principles. The declared tools (Read, Write, Edit, Glob, Grep) are non-executing file operations, and the content contains no commands, scripts, network calls, credential handling, or instructions to run anything. No destructive or exfiltration behavior is present, so listing it carries no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Review my WebXR prototype design: I use smooth locomotion with a joystick and free camera rotation. What should I change to avoid motion sickness?I'm targeting Quest 3 and PCVR. What frame rate, resolution, and frame budget should I design for, and what happens if I drop a frame?My VR scene objects feel too small and the UI text is hard to read. How should I set world scale and size the interface for players?name: vr-ar description: VR/AR development principles. Comfort, interaction, performance requirements. allowed-tools: Read, Write, Edit, Glob, Grep
VR/AR Development
Immersive experience principles.
1. Platform Selection
VR Platforms
| Platform | Use Case | |----------|----------| | Quest | Standalone, wireless | | PCVR | High fidelity | | PSVR | Console market | | WebXR | Browser-based |
AR Platforms
| Platform | Use Case | |----------|----------| | ARKit | iOS devices | | ARCore | Android devices | | WebXR | Browser AR | | HoloLens | Enterprise |
2. Comfort Principles
Motion Sickness Prevention
| Cause | Solution | |-------|----------| | Locomotion | Teleport, snap turn | | Low FPS | Maintain 90 FPS | | Camera shake | Avoid or minimize | | Rapid acceleration | Gradual movement |
Comfort Settings
- Vignette during movement
- Snap vs smooth turning
- Seated vs standing modes
- Height calibration
3. Performance Requirements
Target Metrics
| Platform | FPS | Resolution | |----------|-----|------------| | Quest 2 | 72-90 | 1832x1920 | | Quest 3 | 90-120 | 2064x2208 | | PCVR | 90 | 2160x2160+ | | PSVR2 | 90-120 | 2000x2040 |
Frame Budget
- VR requires consistent frame times
- Single dropped frame = visible judder
- 90 FPS = 11.11ms budget
4. Interaction Principles
Controller Interaction
| Type | Use | |------|-----| | Point + click | UI, distant objects | | Grab | Manipulation | | Gesture | Magic, special actions | | Physical | Throwing, swinging |
Hand Tracking
- More immersive but less precise
- Good for: social, casual
- Challenging for: action, precision
5. Spatial Design
World Scale
- 1 unit = 1 meter (critical)
- Objects must feel right size
- Test with real measurements
Depth Cues
| Cue | Importance | |-----|------------| | Stereo | Primary depth | | Motion parallax | Secondary | | Shadows | Grounding | | Occlusion | Layering |
6. Anti-Patterns
| ❌ Don't | ✅ Do | |----------|-------| | Move camera without player | Player controls camera | | Drop below 90 FPS | Maintain frame rate | | Use tiny UI text | Large, readable text | | Ignore arm length | Scale to player reach |
Remember: Comfort is not optional. Sick players don't play.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/vr-ar-development-principles-msh3usns' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/vr-ar-development-principles-msh3usns/download' --output '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md.part' && mv '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md.part' '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && test -s '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/vr-ar' && cp -R '.skill-downloads/vr-ar-development-principles-msh3usns' '.claude/skills/vr-ar'Cursor
test -f '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && test -s '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/vr-ar' && cp -R '.skill-downloads/vr-ar-development-principles-msh3usns' '.cursor/skills/vr-ar'Codex
test -f '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && test -s '.skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/vr-ar' && cp -R '.skill-downloads/vr-ar-development-principles-msh3usns' '.agents/skills/vr-ar'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/vr-ar-development-principles-msh3usns'openskills read 'vr-ar-development-principles-msh3usns'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/vr-ar-development-principles-msh3usns/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.