godot

Godot

Use this skill to inspect and modify Godot projects with the bundled workflows, scripts, and any available host-native Godot automation tooling, including gameplay presentation work such as art generation, frame animation integration, and project-native integration of provided or separately generated music and story content.

Start

• Verify which Godot automation path is available before planning edits. Prefer any native or mapped Godot tools in the host agent. Use the bundled headless dispatcher only for the supported file and scene operations listed below.
• Resolve project_path to an absolute project directory when a host tool requires it.
• Normalize scene and resource paths to res://... when working directly with the bundled Godot scripts in this skill.
• Inspect unfamiliar projects with any available project-discovery tools, or fall back to reading project.godot, scene files, and scripts directly.
• When the task involves art, music, or story, inspect the existing visual style, palette, audio direction, and narrative format before creating new content.
• If the user does not specify a style, preserve any clearly established project direction first. If there is no established direction to follow, default new visual work to a pixel-art style and keep related presentation choices consistent with it.
• Read references/asset_pipeline.md only when the task involves generated art, cutouts, or frame animation assets.
• Read references/architecture_qframework_lite.md only when the task involves Godot architecture design, modular refactoring, feature boundaries, controller or system or model responsibilities, command and query separation, or QFramework-style structure.
• Read references/architecture_templates.md only when you need a ready folder layout or starter skeletons for Godot GDScript or C# architecture work.
• Read export_presets.cfg before planning export work. Reuse the preset names, bundle identifiers, signing settings, and feature tags that already exist instead of inventing replacements.
• Require a local godot CLI with shell access before using the bundled dispatcher fallback, runtime runner, or CLI export wrapper. The bundled APIs are designed against the current stable Godot docs and verified on Godot 4.7 (compatible with Godot 4.x).
• Read references/export_targets.md only when the task involves packaging, signing, or shipping builds for Android, iOS, Web, Windows, or macOS.
• Read references/gdscript_conventions.md before writing or editing any .gd file. Generated GDScript must parse and boot first-try: annotate every variable, parameter, and return type, and never use := where the right-hand side has no concrete static type ($Node, %Unique, get_node(), instantiate(), Dictionary/Array reads, JSON.parse_string(), null, or a call into an untyped function). Godot rejects those at parse time — with inference_on_variant shipping set to error — so the project will not start at all.
• Read references/debugging.md when the task involves running the project, reading the Godot debugger's errors, and fixing them.
• Read references/automation_api.md when using inspection, resource_batch, project_batch, tileset/tilemap/gridmap/theme/animation/audio-bus authoring, collision/CSG/navmesh baking, glTF export, replication config, unit-test running, import audit, scenario, environment probe, validation, or export preflight APIs.
• Read references/authoring_recipes.md when the task involves shaders/ShaderMaterial, particles, environment/sky, fonts, multiplayer replication, 3D import options, GDExtension, or feature tags — it gives the generic-op recipes and lists what is editor-only and must not be attempted headlessly (LightmapGI/occluder/reflection-probe bakes, VisualShader graphs).
• Read references/vfx_2d.md when the task involves 2D lighting, particles, parallax, trails, paths, or tile-based levels — it also lists the 4.3+ node deprecations (TileMap → TileMapLayer, ParallaxBackground → Parallax2D).
• Read references/game_ui.md when the task involves menus, HUDs, dialogs, inventories, or any Control work — it gives the container-first layout doctrine (the fix for sibling controls piling up at (0, 0)), runnable title/HUD/pause/dialog scene_batch skeletons, a complete game Theme, and the pixel-art UI rules.
• Read references/tscn_format.md whenever a .tscn or .tres will be written or patched as text — a host without shell access cannot run the bundled dispatcher, or an entire new scene is being authored from scratch. Hand-written node hierarchies fail silently: a tree where every node carries parent="." loads with zero errors and stacks every Control at (0,0), and check_project does not detect it.
• Read references/tween.md when adding code-driven juice (punches, fades, shakes); Tweens are runtime-only and ship inside scripts via attach_script.
• Read references/localization.md when translating game text or wiring translation files (note: POT template generation is editor-only in Godot 4.x).
• Read references/ci.md when setting up automated test or export pipelines.
• Install this skill in a folder named godot so the folder name matches name: godot in hosts that validate skill naming.