This skill makes every HUD and menu work on a phone, an ultrawide monitor and a TV, with a mouse or only a gamepad. It decides layout, scaling, focus, screen flow and how the UI listens to game state, while the engine UI skill supplies the nodes, components and styling.
It includes a screen-stack model for menus, a rule that the HUD subscribes to events and sets its initial value once, and checks for focus and for several screen sizes.
What You Get
- Anchor and container guidance with Godot and Unity UGUI examples
- Scaling settings for Godot stretch and Unity CanvasScaler, with the UI Toolkit equivalent
- Safe-area inset code for Godot and a Unity Screen.safeArea approach
- Accessibility minimums: text at least 26 px at 1080p on console and TV, 4.5:1 contrast, and a colour-blind-safe signal
Common Use Cases
- Fixing a health bar or inventory that breaks on ultrawide or phone screens
- Making every menu usable with only a gamepad
- Stopping focus from escaping a modal dialog to buttons behind it
- Replacing per-frame HUD polling with event subscriptions
What Makes It Unique
It names the engine-specific traps that cost hours: set_process_input(false) does not disable a Godot menu, a UGUI scene keeps a StandaloneInputModule after switching to the Input System, pixel-art UI shimmers at fractional scales, and German text runs about 30 percent longer. It pairs with the engine widget skills and says to load both.
Under The Hood
The skill is instructions and one reference file on layout and flow, with no scripts. It tells the agent to inspect the project’s UI settings and screen code, then to run checks: a headless script that opens each screen and fails when nothing has focus, and a launch at three window sizes that saves screenshots, which needs a display or xvfb-run and writes image files. It does not fetch web pages or call APIs. It edits UI scenes and scripts in the project.