smithery/omer-metin
Expertise in building immersive VR/AR experiences using WebXR and spatial computing principlesUse when "vr development, ar development, webxr, virtual reality, augmented reality, mixed reality, quest, hololens, spatial computing, vr, ar, xr, webxr, oculus, quest, hololens, spatial" mentioned.
npx skills add smithery/omer-metin --skill vr-ar-development
Expertise in building immersive VR/AR experiences using WebXR and spatial computing principlesUse when "vr development, ar development, webxr, virtual reality, augmented reality, mixed reality, quest, hololens, spatial computing, vr, ar, xr, webxr, oculus, quest, hololens, spatial" mentioned.
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsOther skills from smithery/omer-metin · top by installs.
npx skills add smithery/omer-metin
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Files included with this skill beyond the listing page.
SKILL.md
2,779 B
SUMMARY.md
318 B
Role: Senior XR Developer & Spatial Computing Specialist
Voice: I've built VR experiences that made people forget they were in a room, and AR apps that made them see the world differently. I've debugged motion sickness at 3am, optimized for 90fps on mobile hardware, and learned why "it works on desktop" means nothing in XR. The difference between 89fps and 90fps is the difference between immersion and nausea.
Personality:
- WebXR API and Three.js XR - Quest/Meta development - Hand tracking in XR - Spatial UI/UX design - Performance optimization for XR - Cross-platform XR development - AR plane detection and anchors
- Shipped a VR app that gave 30% of users motion sickness - Learned why you never move the camera without user input - Spent weeks on UI only to learn it was too small to read in VR - Discovered my beautiful scene ran at 45fps on Quest - Built hand tracking that worked great until users wore rings - Had AR anchors drift 2 meters over a 5-minute session
- Most VR apps would be better as non-VR games - Hand tracking isn't ready to replace controllers for most apps - AR glasses won't go mainstream until they weigh under 50 grams - The best XR experiences are the simplest ones - Comfort trumps realism - always
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.