game_ui_architecture

What problem does it solve?

This Skill helps you design and implement player-facing game UI that stays organized, maintainable, and decoupled from live simulation state in Godot projects.

Core Features & Use Cases

• Retained-mode UI structure: Use Godot Control nodes for menus, HUDs, inventories, dialogs, and other player-facing interfaces.
• Layered UI hierarchy: Separate HUDs, menus, overlays, modals, and tooltips with CanvasLayer-based stacking.
• Stack-based navigation: Manage pause menus and nested screens with push and pop screen flow so players can move back and forth cleanly.
• Presentation-model binding: Read ECS state through view models or presenters instead of binding controls directly to simulation data.
• Theme-driven styling: Apply reusable themes, font settings, and style overrides for consistent UI presentation.
• Use Case: Build a pause menu that opens on top of gameplay, shows player health through a presentation model, and returns to the previous screen without losing state.

Quick Start

Ask the assistant to design a Godot UI architecture for your game using layered CanvasLayers, stack-based screen navigation, and presentation models bound to ECS data.