Three.js Game UI Designer
Build interface states that support play and feel native to the game.
Read By Need
- UI implementation and state patterns:
references/ui-patterns.md.
- Before claiming HUD, menu, responsive, or touch work complete:
references/quality-gates.md.
- Generated 3D menu objects or diegetic props:
../../references/mint-mcp-assets.md.
Use authored HTML/CSS/SVG/Canvas or user-provided assets for ordinary flat UI.
Use Mint MCP only when the live host exposes the required output. Never use
another generation provider.
Workflow
- Inspect desktop/mobile screenshots and inventory gameplay, pause, settings,
loading, fail/retry, win/milestone, and touch states.
- Prioritize survival/status, objective, feedback, then flavor.
- Replace utility cards with game-specific meters, clusters, badges, icons,
alerts, reticles, and modal states.
- Keep dimensions stable; account for text fit, safe areas, touch targets,
hover/pressed/focus/disabled states, and reduced motion.
- Drive UI from game state without duplicating simulation rules.
- Verify relevant states through real input at desktop and mobile sizes.
Final Response
Report states covered, UI intent, controls, screenshots, text-fit/overlap,
safe-area/touch-target evidence, and remaining risks.
1---2name: threejs-game-ui-designer3description: "Design readable, responsive Three.js game HUDs, menus, overlays, touch controls, typography, safe areas, and game-state-driven interface feedback."4metadata:5 source: https://skillmd.com/skills/mintdotgg/threejs-game-ui-designer6---78# Three.js Game UI Designer910Build interface states that support play and feel native to the game.1112## Read By Need1314- UI implementation and state patterns: `references/ui-patterns.md`.15- Before claiming HUD, menu, responsive, or touch work complete:16 `references/quality-gates.md`.17- Generated 3D menu objects or diegetic props:18 `../../references/mint-mcp-assets.md`.1920Use authored HTML/CSS/SVG/Canvas or user-provided assets for ordinary flat UI.21Use Mint MCP only when the live host exposes the required output. Never use22another generation provider.2324## Workflow25261. Inspect desktop/mobile screenshots and inventory gameplay, pause, settings,27 loading, fail/retry, win/milestone, and touch states.282. Prioritize survival/status, objective, feedback, then flavor.293. Replace utility cards with game-specific meters, clusters, badges, icons,30 alerts, reticles, and modal states.314. Keep dimensions stable; account for text fit, safe areas, touch targets,32 hover/pressed/focus/disabled states, and reduced motion.335. Drive UI from game state without duplicating simulation rules.346. Verify relevant states through real input at desktop and mobile sizes.3536## Final Response3738Report states covered, UI intent, controls, screenshots, text-fit/overlap,39safe-area/touch-target evidence, and remaining risks.