domains / families / software-engineering / game-ui-ux

game-ui-ux

separate

Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected engine's UI skill. Use when the user mentions HUD, health bar, main menu, pause menu, settings screen, UI layout, anchors, UI scaling, aspect ratio, safe area, controller/keyboard menu navigation, or wiring UI to game state.

When to use

• Use when building a HUD (health/ammo/score), a menu (main/pause/settings), an inventory or
• Use to fix UI that breaks at other resolutions/aspect ratios, ignores notches/safe areas,
• Use to structure screen flow (title → game → pause → settings) as a stack, not flag soup.

When not to use

• engine-specific UI nodes/components and styling
• visual punch (button pop, damage numbers, shake)
• branching conversation UI
• translating UI strings (localization)
• card/board layout specifics

Skill page

Source