What problem does it solve?
Three.js games built for desktop often break on mobile: touch controls are missing, HUDs overflow small viewports, orientation changes reset gameplay, and performance collapses on low-end devices. This Skill provides a structured playbook for making a Three.js game work properly on mobile web.
Core Features & Use Cases
- Touch Control Design: Implement movement controls, reachable primary actions, target selection, cancel/reset paths, and non-drag inventory alternatives with feedback for held, unavailable, and queued actions.
- Responsive HUD Layout: Design portrait and landscape layouts that keep status, target data, inventory, tooltips, and dialogs legible without covering the playfield, and survive orientation changes without resetting state.
- Performance and QA Discipline: Apply device-appropriate quality defaults, adaptive decorative effects, and test multi-touch, long sessions, audio unlock, background return, reduced motion, and low-end quality in real mobile-size viewports.
- Use Case: You have a desktop-first Three.js game and need to ship it to mobile browsers. Use this Skill to add touch controls, fix safe-area overlaps, and run a mobile QA pass before release.
Quick Start
Use the build-mobile-threejs-games skill to adapt my Three.js game for mobile touch controls and responsive HUD layouts.
