Game UI/UX

This is the canonical generic game-interface contract. It combines the pictured game-ui-design, game-ui-ux, and Three.js game-UI planning lanes without duplicating engine widgets or the project-specific Open Design takeover workflow.

When to use this skill

Use it to:

• design or review a HUD, menu, inventory, shop, map, settings screen, or overlay;
• map player decisions to information priority and visibility rules;
• design screen flow, pause/overlay behavior, focus order, and back/cancel behavior;
• support mouse, keyboard, controller, touch, and assistive input consistently;
• handle aspect ratios, safe areas, text scaling, localization, and content expansion;
• replace per-frame UI polling with a documented state/event contract;
• compare mockups against real runtime states and target devices;
• build a verification matrix before engine implementation.