agentleFS
Sign inStart free
xenitV1xenitV1/Antigravity-Workflows/skills/game-development/vr-ar/SKILL.md

vr-ar

Skill130 starsChanged 10 months agoMITView on GitHub

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

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test with real measurements

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free