AGENT SKILL

vr-ar

VR/AR development principles. Comfort, interaction, performance requirements.

License 许可
MIT
最近更新
2026-10-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
vr-ar
description
VR/AR development principles. Comfort, interaction, performance requirements.
allowed-tools
Read, Write, Edit, Glob, Grep

03 SKILL.md 正文

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.

04 同仓库更多 Skills

marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

zapier-make-patterns

No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power

★ 0
marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 0
marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

workflow-automation

Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility

★ 0
marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

trigger-dev

Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

★ 0
marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

slack-automation

Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.

★ 0
marnixGeerkens
marnixGeerkens/rocketlauncher-claude-code

rote

Compile a proven agent skill (a SKILL.md plus references) into a deterministic pipeline that runs without an LLM in the loop, then serve it back to Claude as an MCP tool. Use when: rote, compile this skill, turn this skill into a workflow, make this skill deterministic, make this skill cheaper or faster, harden this skill for production, run this skill as a background job.

★ 0