vr-ar
VR/AR development principles. Comfort, interaction, performance requirements.
Best use case
vr-ar is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
VR/AR development principles. Comfort, interaction, performance requirements.
Teams using vr-ar should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vr-ar/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How vr-ar Compares
| Feature / Agent | vr-ar | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
VR/AR development principles. Comfort, interaction, performance requirements.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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.
Related Skills
async-python-patterns
Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.
slack-automation
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
gitops-workflow
Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.
github-automation
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
github-actions-templates
Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
tanstack-query-expert
Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.
tailwind-design-system
Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility.
sveltekit
Build full-stack web applications with SvelteKit — file-based routing, SSR, SSG, API routes, and form actions in one framework.