live-editor

Estrelas9

Forks1

Atualizado13 de julho de 2026 às 02:55

Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

NotNull92

NotNull92/hera-agent-godot

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	live-editor
description	Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state.

Hera live Godot workflow

Use Hera only with a running Godot editor that has the Hera Agent Godot addon enabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source of truth for live editor and runtime state.

Start with the live editor

Run hera status. If no live editor is found, ask the user to enable the addon under Project Settings → Plugins; do not infer editor state from files.
If multiple editors are found, run hera instances. Pass hera --instance <pid> for any mutation.
Before UI work, run hera guidance ui and follow its returned mode.

Keep reads small and writes safe

Default output is compact. Prefer hera --ids scene tree, selected node get --prop/--props, scoped game ui tree, and game qa discover before full dumps.
Use node add/set/remove and signal connect/disconnect for normal editor changes; Godot records those as undoable steps. Prefer them to eval, whose expression can have side effects and is not undoable.
Scene, resource, script, import, and project-setting commands persist to disk. game node set/call, game click, and game input affect only the running game and disappear when it stops.
Keep one editor per project. After direct .tscn edits, stop the game, hera scene reload, then save through the editor.

Prove the result

After a change, read the changed property or node tree. After a run, check hera output --type error or hera diagnostics.
For visual/UI work, use game ui tree, semantic game click, and hera screenshot --runtime --analyze. For prompt requirements, prefer a game qa --file scenario with requirements and per-step covers.
After editing GDScript, run that project's headless --check-only gate when available, then re-check diagnostics.

Hera sends any configured HERA_AGENT_GODOT_TOKEN automatically. Never print or place that token in project files. For the complete command reference, see the Hera repository's docs/COMMANDS.md.

Mais deste repositório

mesmo repositório

ui-theme-qa

NotNull92/hera-agent-godot

Use this skill to find and fix undisciplined Control-node UI in a Godot project — spacing that follows no ladder, font sizes with no modular scale, near-duplicate colours, and text that fails WCAG contrast — by measuring the live editor with the `hera` CLI and snapping theme tokens to a reference corpus. It also reports (without changing) inert container wrappers and decorative nodes. Triggers: "clean up the UI spacing/type/contrast", "the UI values look arbitrary", "tidy the Godot UI", "check UI contrast", or any request to mechanically remove statistical UI-design defects without a redesign. Reductive only; edits per-node theme overrides (undoable), never copy or layout content.

2026-07-219

name	live-editor
description	Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state.

Hera live Godot workflow

Start with the live editor

Run hera status. If no live editor is found, ask the user to enable the addon under Project Settings → Plugins; do not infer editor state from files.
If multiple editors are found, run hera instances. Pass hera --instance <pid> for any mutation.
Before UI work, run hera guidance ui and follow its returned mode.

Keep reads small and writes safe

Default output is compact. Prefer hera --ids scene tree, selected node get --prop/--props, scoped game ui tree, and game qa discover before full dumps.
Use node add/set/remove and signal connect/disconnect for normal editor changes; Godot records those as undoable steps. Prefer them to eval, whose expression can have side effects and is not undoable.
Scene, resource, script, import, and project-setting commands persist to disk. game node set/call, game click, and game input affect only the running game and disappear when it stops.
Keep one editor per project. After direct .tscn edits, stop the game, hera scene reload, then save through the editor.

Prove the result

After a change, read the changed property or node tree. After a run, check hera output --type error or hera diagnostics.
For visual/UI work, use game ui tree, semantic game click, and hera screenshot --runtime --analyze. For prompt requirements, prefer a game qa --file scenario with requirements and per-step covers.
After editing GDScript, run that project's headless --check-only gate when available, then re-check diagnostics.

Hera sends any configured HERA_AGENT_GODOT_TOKEN automatically. Never print or place that token in project files. For the complete command reference, see the Hera repository's docs/COMMANDS.md.