New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Godot UI Integration

by zimo-xiao-zheng in zimo-xiao-zheng/godot-ui-integration

Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter.

MITAuto-check passedGame Development

Install Godot UI Integration

skills CLI
$ npx skills add zimo-xiao-zheng/godot-ui-integration --skill godot-ui-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zimo-xiao-zheng/godot-ui-integration godot-ui-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
godot-ui-integration
GitHub stars
285
Token cost
~1.5k tokens
SKILL.md length
663 words
Files
12 (incl. scripts, references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter.

  • Works in 4 steps: Read the project instructions and… → Inspect the target viewport, existing… → Use the Godot MCP first for engine… → …
  • Complete Godot UI integration
  • SKILL.md covers Route the request, Required project checks, Implementation invariants and Workflow, plus 2 more sections
  • Runs Python scripts from its folder; calls python

What it does

Godot UI Integration is an agent skill from zimo-xiao-zheng/godot-ui-integration. Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter. Use for complete Godot UI integration; use ordinary Godot UI guidance for isolated node or layout questions that do not require an end-to-end visual workflow.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `references/strict-reference-parity.md`).

It sits in Game Development, covering Game development. It works with Godot. The repository describes itself as: A Codex skill for building Godot UI from approved designs with editor-visible scenes and runtime visual-parity checks. The licence is MIT.

When your agent uses it

  • Complete Godot UI integration
  • Use ordinary Godot UI guidance for isolated node
  • Layout questions that do not require an end-to-end visual workflow

Example prompts

  • “/godot-ui-integration”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the project instructions and canonical UI/navigation documentation.
  2. Inspect the target viewport, existing scenes, themes, input patterns, data sources, and asset directories.
  3. Use the Godot MCP first for engine inspection and edits. If it is unavailable, diagnose and attempt reconnection before using a local…
  4. Record the approved reference, its dimensions, the target screen or overlay, and the intended entry and exit paths.

What it can do on your machine

Read from SKILL.md and the folder at commit 346fa17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 5 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Godot UI Integration loads about 1.5k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 663 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from zimo-xiao-zheng/godot-ui-integration at commit 346fa17, republished under its MIT licence (© zimo-xiao-zheng). 663 words, ~1,498 tokens.

Download SKILL.mdSave it as .claude/skills/godot-ui-integration/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
godot-ui-integration
description
Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter. Use for complete Godot UI integration; use ordinary Godot UI guidance for isolated node or layout questions that do not require an end-to-end visual workflow.

Godot UI Integration

Turn an approved UI direction into editor-visible Godot scenes, connected behavior, and verified runtime output.

Route the request

  • If the user already approved a design or supplied the exact reference to implement, lock that reference and proceed.
  • If the visual direction is new or materially changing, prepare one composed preview and obtain approval before producing final assets or editing scenes.
  • If the user asks for exact, strict, pixel-close, or design-faithful reproduction, read references/strict-reference-parity.md completely before editing.
  • For read-only diagnosis, inspect and report without changing project files.

After the composed preview is approved, continue through asset preparation, scene construction, binding, and validation. Pause only when the approved composition must change, asset rights are unclear, validation remains blocked after targeted retries, or gameplay behavior would expand beyond the requested UI scope.

Required project checks

Before editing:

  1. Read the project instructions and canonical UI/navigation documentation.
  2. Inspect the target viewport, existing scenes, themes, input patterns, data sources, and asset directories.
  3. Use the Godot MCP first for engine inspection and edits. If it is unavailable, diagnose and attempt reconnection before using a local script, CLI, or UI fallback; report the failure and fallback.
  4. Record the approved reference, its dimensions, the target screen or overlay, and the intended entry and exit paths.

Implementation invariants

  • Treat .tscn scenes as the visual source of truth. Every formal player-facing screen or major overlay must be directly openable with its representative composition visible before _ready() runs.
  • Runtime code may populate data, localized text, textures, availability, selection, and transient feedback. It must not construct or relocate the primary layout procedurally.
  • Give distinct formal screens distinct scenes; inherited scenes are acceptable. Serialize screen-specific hierarchy, visibility, anchors, offsets, styles, and representative state.
  • Keep dynamic names, prices, counts, statistics, labels, lock states, and localized strings as Godot nodes or runtime data rather than baking them into raster art.
  • Preserve the approved reference's silhouette, material, texture, edge treatment, proportions, and hierarchy. Use native Godot primitives only where the design itself is visually simple.
  • Store final resources inside the Godot project. Do not leave scenes referencing temporary generation or working directories.
  • Reuse project conventions unless doing so would contradict the approved design or the user's asset-source constraints.
Show full SKILL.md (326 more words)Show less

Workflow

  1. Survey: identify the affected scenes, scripts, data, navigation, input, viewport, safe areas, fonts, and reusable components.
  2. Lock the design: choose the exact approved reference and map major regions, dynamic fields, hit targets, ownership, and responsive behavior.
  3. Plan assets: classify each visual as direct extraction, reference-guided generation, reconstruction, reusable project art, or native Godot styling. Confirm source rights before reuse.
  4. Prepare assets: create one final file per asset, remove temporary backgrounds, preserve intended transparency, normalize display size, and avoid destructive whole-canvas stretching.
  5. Build scenes: serialize the formal composition and reusable repeated components in .tscn; keep decorative children from intercepting input.
  6. Bind behavior: connect data, navigation, disabled/empty/error states, persistent selection, controller/keyboard focus, and save boundaries without rebuilding the authored layout.
  7. Validate: inspect the editor scene, run the UI at the target resolution, exercise interactions, check errors, compare against the reference, and update the project UI documentation.

Validation helpers

The included Python tools require Pillow:

bash
python -m pip install -r requirements.txt

  • Inspect alpha and visible bounds:

    bash
    python scripts/alpha_audit.py path/to/asset.png

  • Build a contact sheet for candidate review:

    bash
    python scripts/contact_sheet.py "path/to/candidates/*.png" --out path/to/contact-sheet.png

  • Compare an approved reference with a runtime capture:

    bash
    python scripts/reference_parity_audit.py reference.png runtime.png --out path/to/parity.png

  • Audit panel-like textures for deformation and invalid nine-slice margins:

    bash
    python scripts/stretch_audit.py --project-root path/to/project --scene res://path/to/screen.tscn

  • Remove an edge-connected white background from an approved cutout:

    bash
    python scripts/white_bg_to_alpha.py --input source.png --out asset.png

Review generated outputs visually. Passing deterministic checks does not prove design fidelity.

Completion gate

Do not report completion until:

  • the formal scene is editor-visible before runtime binding;
  • the runtime path reaches and exits the UI correctly;
  • dynamic content and interaction states behave correctly;
  • there are no new parse, import, or runtime errors caused by the change;
  • strict-reference work includes a same-resolution comparison artifact and disclosed deviations;
  • the canonical project UI documentation reflects the implemented behavior and validation evidence.

Report the changed scenes, scripts, assets, runtime captures, validation commands, MCP status, known deviations, and any deferred product decisions.

© zimo-xiao-zheng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts, references) in the repository root of zimo-xiao-zheng/godot-ui-integration.

  • SKILL.md
  • .gitignore
  • LICENSE
  • README.md
  • agents/openai.yaml
  • references/strict-reference-parity.md
  • requirements.txt
  • scripts/alpha_audit.py
  • scripts/contact_sheet.py
  • scripts/reference_parity_audit.py
  • scripts/stretch_audit.py
  • scripts/white_bg_to_alpha.py

Open the folder on GitHubat commit 346fa17

Compare with similar skills

Godot UI Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Godot UI Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Godot UI Integration this skillzimo-xiao-zheng/godot-ui-integration285—~1.5kAutomated safety check: PassMIT
Godot Gdscript Patterns925236118/AlphaAgent10310 repos~5kAutomated safety check: PassMIT
2D Map and Scene Generator0x0funky/agent-sprite-forge4.4k—~2.9kAutomated safety check: PassMIT
Godot Wechat Minigame Adaptergodothub/godot-minigame187—~1.5kAutomated safety check: PassMIT
AI Game Art Pipelineybuild-ai/ai-game-art-pipeline-skill297—~1.1kAutomated safety check: PassMIT
MCP DriverRandallLiuXin/GodotMaker5501 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Godot Gdscript Patterns

    925236118/AlphaAgent

    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization.

    103 GitHub starsUsed in 10 repos~5k tokens
    Game DevelopmentAuto-check passed

  • 2D Map and Scene Generator

    0x0funky/agent-sprite-forge

    Plans and builds 2D game maps and scenes, from tilemaps and parallax backgrounds to HD-2D plates, with collision checks, a playable HTML preview and Tiled, Godot or LDtk export.

    4.4k GitHub stars~2.9k tokensUpdated 5 days ago
    Game DevelopmentAuto-check passed

  • Godot Wechat Minigame Adapter

    godothub/godot-minigame

    Apply the bundled self-contained Godot WeChat Mini Game adapter kit to an official Godot checkout.

    187 GitHub stars~1.5k tokensUpdated 26 days ago
    Game DevelopmentAuto-check passed

  • AI Game Art Pipeline

    ybuild-ai/ai-game-art-pipeline-skill

    Provider-neutral open-source skill for planning and producing game-runtime art assets and animation: static props/icons, canonical character sheets, combat sprites, 3D/video motion references…

    297 GitHub stars~1.1k tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed

  • MCP Driver

    RandallLiuXin/GodotMaker

    Runtime debugging and live project inspection via godot-mcp.

    550 GitHub starsUsed in 1 repo~1.1k tokens
    Game DevelopmentAuto-check passed

  • Camera Systems

    ukanwat/overtime

    Build game cameras that feel good — 2D follow with a deadzone, look-ahead, smoothing, and level-bounds clamping; 3D third-person orbit with collision and first-person look; plus multi-target framing…

    387 GitHub starsUsed in 1 repo~2.2k tokens
    Game DevelopmentAuto-check passed

Works with

Categories

Questions about Godot UI Integration

What does Godot UI Integration do?

Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter. Godot UI Integration is an agent skill from zimo-xiao-zheng/godot-ui-integration. Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter.

When should I use Godot UI Integration?

Godot UI Integration fits situations like: complete Godot UI integration; use ordinary Godot UI guidance for isolated node; layout questions that do not require an end-to-end visual workflow.

How do I install Godot UI Integration in Claude Code?

Run `npx skills add zimo-xiao-zheng/godot-ui-integration --skill godot-ui-integration -a claude-code`. Or copy the skill folder (the zimo-xiao-zheng/godot-ui-integration repository) into .claude/skills/godot-ui-integration in your project. Claude Code loads it when a task matches its description.

How do I install Godot UI Integration in Codex?

Run `npx skills add zimo-xiao-zheng/godot-ui-integration --skill godot-ui-integration -a codex`. Or copy the skill folder (the zimo-xiao-zheng/godot-ui-integration repository) into .agents/skills/godot-ui-integration in your project. Codex loads it when a task matches its description.

Can I use Godot UI Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zimo-xiao-zheng/godot-ui-integration --skill godot-ui-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/godot-ui-integration, .gemini/skills/godot-ui-integration, .github/skills/godot-ui-integration and .opencode/skills/godot-ui-integration in your project.

What does Godot UI Integration need to run?

Going by SKILL.md and its folder, Godot UI Integration needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Godot UI Integration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Godot UI Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Godot UI Integration use?

Godot UI Integration is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Godot UI Integration use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Godot UI Integration?

Skills that share tags, products or a category with Godot UI Integration: Godot Gdscript Patterns (925236118/AlphaAgent, 103 stars), 2D Map and Scene Generator (0x0funky/agent-sprite-forge, 4.4k stars), Godot Wechat Minigame Adapter (godothub/godot-minigame, 187 stars) and AI Game Art Pipeline (ybuild-ai/ai-game-art-pipeline-skill, 297 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Godot UI Integration?

zimo-xiao-zheng (a GitHub user) maintains it in zimo-xiao-zheng/godot-ui-integration, which has 285 GitHub stars. The repository was last updated on August 23, 2026.

Source: zimo-xiao-zheng/godot-ui-integration on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.