Skip to content
Automation
Skill

/ui

Reviews Godot UI/Control implementation for known pitfalls. Triggers AFTER implementation, when code involves Control, Container, HBoxContainer, VBoxContainer, GridContainer, MarginContainer, ScrollContainer, PanelContainer, Button, Label, LineEdit, TextEdit, OptionButton,

From plugin
godotmaker
51141 skills7 agents14 hooks
Install
$ npx -y skills add RandallLiuXin/GodotMaker --skill ui --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/ui

Context preview

The summary Claude sees to decide when to auto-load this skill.

Reviews Godot UI/Control implementation for known pitfalls. Triggers AFTER implementation, when code involves Control, Container, HBoxContainer, VBoxContainer, GridContainer, MarginContainer, ScrollContainer, PanelContainer, Button, Label, LineEdit, TextEdit, OptionButton,

SKILL.md

ui.SKILL.md
name: ui-review
description: |
  Reviews Godot UI/Control implementation for known pitfalls.
  Triggers AFTER implementation, when code involves Control, Container, HBoxContainer,
  VBoxContainer, GridContainer, MarginContainer, ScrollContainer, PanelContainer,
  Button, Label, LineEdit, TextEdit, OptionButton, TabContainer, CanvasLayer,
  Theme, StyleBox, focus_mode, mouse_filter, grab_focus, or gui_input.
  Do NOT use this skill for planning or teaching — only for post-implementation review.

UI Review

Post-implementation reviewer for Godot UI code.

When to trigger

After UI-related code is written or modified. Look for:

  • Container nodes (HBox, VBox, Grid, Margin, Panel, Center, Scroll, Tab, Split)
  • Control properties (focus_mode, mouse_filter, custom_minimum_size, scale)
  • Theme resources or theme overrides
  • Focus navigation (grab_focus, focus_neighbor_*)
  • CanvasLayer with UI content
  • z_index on Control nodes

Review process

1. Read `gotchas.md` 2. Scan the implemented code against each gotcha 3. For each hit: cite gotcha ID, show offending code, provide fix 4. If no hits, report clean 5. Optionally run `checklist.md` static checks

When you need specific API details, delegate to the **godot-api** skill.

Ships withgodotmaker

Autonomous text-to-game pipeline for Godot, powered by Claude Code,Codex,Opencode

Get the whole plugin