ui-review

Godot UI pitfalls are caught by scanning Control implementations post-change against a known gotchas list, matching offending code to specific issues and suggesting fixes for layout behavior, focus navigation, and theme inheritance.

Godot Control layout behaves unexpectedly due to known pitfalls in container usage and mouse_filter settings. Reviewing the scene code against documented gotchas identifies the specific offending lines and provides corrective actions to fix the layout behavior.

Godot theme inheritance issues are checked by reviewing scenes with Theme or StyleBox usage for known pitfalls. The review process matches detected problems to gotcha IDs, highlights the offending code, and suggests fixes to resolve inheritance conflicts.

Static checks can run on Godot UI code using an optional checklist mapped to known gotchas, detecting mouse_filter and input interaction problems. This provides static detection alongside runtime-oriented test guidance for modified Control scenes.

The best way to prevent hard-to-debug Godot UI issues is running an evidence-based post-implementation review that scans Control, CanvasLayer, and Theme usage for known pitfalls, identifying exact gotcha IDs and providing targeted corrective actions.

Reviewing Godot UI code can delegate API details to a godot-api skill when needed, while the core review focuses on matching container, focus, and theme inheritance pitfalls to gotcha IDs with cited offending code and suggested fixes.