godot-game-ui-designer

name	godot-game-ui-designer
description	Design premium Godot game UI. Use for HUDs, menus, overlays, pause/win/lose screens, settings, icon controls, touch UI, typography, responsive layout, safe areas, text fit, and UI/world cohesion.

Godot Game UI Designer

Godot Reference Links

Targets Godot 4.6.x (latest stable 4.6.3, June 2026). These links use /en/stable/, so they always resolve to the current stable docs — fetch them for up-to-date nodes, classes, and method signatures rather than relying on memory.

• Latest stable docs: https://docs.godotengine.org/en/stable/
• Class reference: https://docs.godotengine.org/en/stable/classes/index.html
• User interface (GUI): https://docs.godotengine.org/en/stable/tutorials/ui/index.html
• Size and anchors: https://docs.godotengine.org/en/stable/tutorials/ui/size_and_anchors.html
• Using containers: https://docs.godotengine.org/en/stable/tutorials/ui/gui_containers.html
• Multiple resolutions (stretch, scale, safe area): https://docs.godotengine.org/en/stable/tutorials/rendering/multiple_resolutions.html
• Control class reference: https://docs.godotengine.org/en/stable/classes/class_control.html

Purpose

Make game UI intentional, readable, responsive, and genre-specific.

Workflow

Load references/ui-patterns.md as the first action when designing HUDs, menus, overlays, pause/win/lose screens, settings, touch controls, typography, responsive layout, safe areas, text fit, icons, or UI/world cohesion. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark the UI phase complete while this reference is skipped for interface work.

Load references/checklists/game-ui-quality.md, references/checklists/hud-readability.md, and references/checklists/responsive-ui-fit.md before claiming UI/HUD/menu work is complete. Load references/checklists/mobile-input.md when touch controls or mobile safe areas are in scope.

Load references/prompt-templates.md only when the user asks for reusable prompts, a UI pass prompt, or a task template.

Load godot-image-generator when logos, icons, GUI art, faction marks, menu backgrounds, decals, or 2D HUD assets would improve quality. Use godot-3d-generator only for 3D menu/showcase objects or diegetic 3D UI props, not normal flat HUD elements.

The packaged scaffold's HUD at assets/godot-game/scripts/systems/hud.gd (a CanvasLayer + Control with a touch stick and dash button, driven by game state) is the concrete reference for how HUD code binds to the simulation. Cite it; do not recreate it.

1. Capture/inspect desktop and mobile viewport screenshots.
2. Inventory UI states: gameplay, pause, settings, fail/retry, win/milestone, loading, touch controls.
3. Define hierarchy: survival/status, objective, feedback, flavor.
4. Replace utility stat cards with authored clusters, meters, badges, icons, alerts, and modal states.
5. Use stable dimensions via Container nodes, safe-area padding, text-fit constraints, and hover/pressed/focus/disabled theme states.
6. Wire UI to game state, not duplicated rules.
7. Verify text fit, overlap, safe areas, touch targets, responsive screenshots, and real state changes.

Common Failure Modes

• Generic dashboard/stat-card HUD.
• UI covers player/threats.
• Text shifts/clips on mobile.
• Decorative panels reduce readability.
• Touch controls look right but do not emit intents.

Final Response

Report the reference ledger, UI state checklist, UI intent, states covered, files changed, screenshots, text-fit/overlap checks, safe-area/touch-target evidence, controls, and remaining risks.