ui-review

Name: ui-review
Availability: InStock
Author: LiuXin

Review Godot UI Control implementations for layout, focus, input, and theme pitfalls.

511|44|Updated Apr 13, 2026

Search Tags:#ui review #godot #focus management #control nodes #layout pitfalls #mouse_filter #theme inheritance

Ready to run

npx skills add https://github.com/RandallLiuXin/GodotMaker --skill ui-review-randallliuxin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-review
Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/reviewer/ui
Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill ui-review-randallliuxin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents common, hard-to-debug Godot UI issues by reviewing Control and UI-related implementation after changes are made, so you can fix layout, focus, input, and theme problems early.

Core Features & Use Cases

Post-implementation UI gotcha review: Scans Godot UI code for known pitfalls in Control/Container usage and typical runtime behaviors.
Evidence-based fixes: For each detected issue, it identifies the gotcha ID, highlights the offending code, and provides a corrective action.
Optional static checklist: Can run additional static checks mapped to the same gotchas, plus runtime-oriented test guidance.

Quick Start

Ask the AI to run the ui-review skill on your Godot UI scene code after you implement the Control/Container changes.

Frequently Asked Questions about ui-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I catch common Godot UI layout and focus pitfalls after writing Control node code?▼

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.

Why does my Godot Control node layout behave unexpectedly inside containers?▼

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.

How do I check Godot theme inheritance issues in my UI scenes?▼

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.

Can I run static checks on Godot UI code to find mouse input handling problems?▼

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.

What is the best way to prevent hard-to-debug Godot UI issues before shipping?▼

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.

Does reviewing Godot UI code require an external API reference to fix container pitfalls?▼

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.