.agents/skills/game-development/vr-ar/SKILL.md
VR/AR development principles. Comfort, interaction, performance requirements.
npx skillsauth add JoelBonito/gestion-chs vr-arInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Immersive experience principles.
| Platform | Use Case | |----------|----------| | Quest | Standalone, wireless | | PCVR | High fidelity | | PSVR | Console market | | WebXR | Browser-based |
| Platform | Use Case | |----------|----------| | ARKit | iOS devices | | ARCore | Android devices | | WebXR | Browser AR | | HoloLens | Enterprise |
| Cause | Solution | |-------|----------| | Locomotion | Teleport, snap turn | | Low FPS | Maintain 90 FPS | | Camera shake | Avoid or minimize | | Rapid acceleration | Gradual movement |
| Platform | FPS | Resolution | |----------|-----|------------| | Quest 2 | 72-90 | 1832x1920 | | Quest 3 | 90-120 | 2064x2208 | | PCVR | 90 | 2160x2160+ | | PSVR2 | 90-120 | 2000x2040 |
| Type | Use | |------|-----| | Point + click | UI, distant objects | | Grab | Manipulation | | Gesture | Magic, special actions | | Physical | Throwing, swinging |
| Cue | Importance | |-----|------------| | Stereo | Primary depth | | Motion parallax | Secondary | | Shadows | Grounding | | Occlusion | Layering |
| ❌ 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.
tools
n8n workflow automation principles, patterns, and validation. Expression syntax, node configuration, MCP tools usage, code node patterns.
testing
# Example Skill > Template skill for specialist squads. Replace with your domain-specific knowledge. ## Overview This skill provides domain-specific knowledge and patterns for the squad. ## When to Use - When the squad needs domain expertise - When applying domain-specific patterns - When reviewing domain-related outputs ## Key Principles 1. **Principle 1:** Description of the first principle 2. **Principle 2:** Description of the second principle 3. **Principle 3:** Description of the th
development
Web application testing principles. E2E, Playwright, deep audit strategies.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".