sickn33/agentic-awesome-skills/vr-ar

VR/AR Development

Immersive experience principles.

1. Platform Selection

VR Platforms

AR Platforms

2. Comfort Principles

Motion Sickness Prevention

Comfort Settings

• Vignette during movement
• Snap vs smooth turning
• Seated vs standing modes
• Height calibration

3. Performance Requirements

Historical hardware examples

Panel resolution is not the recommended render-target resolution. Verify supported refresh modes, runtime scaling and device support before setting a budget.

Frame Budget

• VR requires consistent frame times
• Dropped frames can produce judder; reprojection does not remove the need for stable timing
• 90 FPS = 11.11ms budget

4. Interaction Principles

Controller Interaction

Hand Tracking

• More immersive but less precise
• Good for: social, casual
• Challenging for: action, precision

5. Spatial Design

World Scale

• Calibrate engine world scale against real meters; engine unit conventions differ
• Objects must feel right size
• Test with real measurements

Depth Cues

6. Anti-Patterns

Remember: Comfort is not optional. Sick players don't play.

When to Use

Use when designing immersive locomotion, spatial interaction and comfort settings, or measuring frame times on a target headset.

Example

User request:

Use @vr-ar for this task: VR/AR development principles.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Verification

Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.