Godot UI

Build interfaces from layout rules, reusable visual resources, and explicit interaction states. Do not solve a responsive layout with a pile of coordinates or make pointer input the only usable path.

Inspect Before Editing

Complete this inspection before changing scenes, scripts, themes, or project settings.

1. Locate project.godot and confirm the project root. Read config/features, display base size, stretch mode and aspect, GUI theme settings, localization settings, and Input Map actions.
2. Run the project's established Godot executable with --version when available. Use APIs and Inspector property names from that exact Godot 4.x release.
3. Inspect representative UI scenes and scripts. Record root types, CanvasLayer use, anchor and container patterns, size flags, unique node names, signal connection style, typed GDScript conventions, scene composition, and naming.
4. Inspect existing .tres themes, fonts, font fallbacks, icons, localization files, settings for UI scale, and all interaction states already defined.
5. Run the current UI at its intended design size, smallest supported size, largest practical size, and unusual aspect ratios. Test at least one longer locale if translations exist.
6. Navigate without a mouse. Record initial focus, Tab order, directional neighbors, accept/cancel behavior, focus visibility, and any controls that trap or lose focus.

Do not overwrite project-wide stretch, theme, or input settings to fix one scene without confirming the effect on every existing interface.

Core Layout Rules