Build, tune, or test a Three.js game for mobile web. Use for touch movement, action controls, target selection, touch inventory, safe areas, portrait/landscape layouts, responsive HUD, battery/performance budgets, and real mobile browser QA.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Treat mobile as a primary control and performance surface.
Provide a clear movement control, reachable primary actions, target selection, cancel/reset paths, and non-drag alternatives for inventory. Keep controls out of unsafe areas, avoid overlapping action zones, and show feedback for held, unavailable, and queued actions.
Design for representative portrait and landscape viewports. Keep vital status, target data, inventory, tooltips, and dialogs legible without covering the playfield. Support orientation changes without resetting gameplay state.
Use device-appropriate quality defaults and adaptive decorative effects. Test touch targets, multi-touch, long sessions, audio unlock, pause/background return, reduced motion, low-end quality, and actual mobile-size viewports in the repository-approved browser.
46abf78
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.