Skip to content
cccskills
FreePublished on GitHub

vr-ar

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

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

VR/AR Development

Immersive experience principles.


1. Platform Selection

VR Platforms

PlatformUse Case
QuestStandalone, wireless
PCVRHigh fidelity
PSVRConsole market
WebXRBrowser-based

AR Platforms

PlatformUse Case
ARKitiOS devices
ARCoreAndroid devices
WebXRBrowser AR
HoloLensEnterprise

2. Comfort Principles

Motion Sickness Prevention

CauseSolution
LocomotionTeleport, snap turn
Low FPSMaintain 90 FPS
Camera shakeAvoid or minimize
Rapid accelerationGradual movement

Comfort Settings

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

3. Performance Requirements

Target Metrics

PlatformFPSResolution
Quest 272-901832x1920
Quest 390-1202064x2208
PCVR902160x2160+
PSVR290-1202000x2040

Frame Budget

  • VR requires consistent frame times
  • Single dropped frame = visible judder
  • 90 FPS = 11.11ms budget

4. Interaction Principles

Controller Interaction

TypeUse
Point + clickUI, distant objects
GrabManipulation
GestureMagic, special actions
PhysicalThrowing, 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

CueImportance
StereoPrimary depth
Motion parallaxSecondary
ShadowsGrounding
OcclusionLayering

6. Anti-Patterns

❌ Don't✅ Do
Move camera without playerPlayer controls camera
Drop below 90 FPSMaintain frame rate
Use tiny UI textLarge, readable text
Ignore arm lengthScale to player reach

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

2D game development principles. Sprites, tilemaps, physics, camera.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

3D game development principles. Rendering, shaders, physics, cameras.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

See all skills by umairinayat

Report a problem with this skill