ericrisco/rsc-harness / skills/godot
godot
VerifiedUse when writing, reviewing, or debugging Godot 4.x games in GDScript or C# — scenes, nodes, custom Resources, autoload/EventBus signals, typed GDScript, CharacterBody2D/3D movement, GUT/gdUnit4 — or porting Godot 3 APIs to 4. NOT Unity/Unreal (that is `unity`/`unreal`), NOT `.gdshader` code (`gamedev-shaders`), NOT GDExtension C++ tooling (`cpp`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.1 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 4.6 KB |
| references/export-and-testing.md | markdown | 4.9 KB |
| references/gdscript-style.md | markdown | 3.2 KB |
| references/godot3-to-4-traps.md | markdown | 5.0 KB |
| references/nodes-scenes-resources.md | markdown | 5.0 KB |
evals/cases.yaml
View on GitHubskill: godot
should_trigger:
- prompt: "Write a Godot 4 top-down player controller for a CharacterBody2D with 8-direction movement and a dash."
why: "Core use case: authoring a typed GDScript CharacterBody2D using the velocity + move_and_slide() flow."
- prompt: "My CharacterBody2D just won't move — I call move_and_slide(velocity) every frame and nothing happens. What's wrong?"
why: "Symptom-only trigger routing here via the Godot 4 velocity-property + no-arg move_and_slide fix (they passed the Godot 3 positional arg)."
- prompt: "Convert this Godot 3 script to Godot 4 — it uses onready, yield, .instance() and connect(\"hit\", self, \"_on_hit\")."
why: "The version-contract ban-list is the skill's center of gravity; each named API has a modern replacement here."
- prompt: "How do I connect a signal between two nodes in Godot and pass the health value along?"
why: "Signals via Callable (node.sig.connect / .emit) with typed params is a named trigger."
- prompt: "Set up an autoload EventBus in Godot so my enemies can broadcast that they died without referencing the score UI."
why: "Autoload/singleton + EventBus decoupling pattern is explicitly owned by this skill."
- prompt: "My GDScript won't type-check — how do I properly type an Array of a custom class and cast a colliding body?"
why: "Static typed GDScript (typed Arrays, `as` casts, typed params/returns) is a core section."
- prompt: "Show me the same Godot player script in both GDScript and C#, including how the signal and export differ."
why: "GDScript ↔ C# parity (partial class, [Export]/[Signal], base._Ready()) is a first-class deliverable."
- prompt: "Escribe un script de Godot 4 para que un CharacterBody3D salte y tenga gravedad."
why: "Spanish trigger for a Godot 4 CharacterBody3D controller — squarely this skill."
should_not_trigger:
- prompt: "Write a Unity C# MonoBehaviour that moves a Rigidbody with FixedUpdate and input."
route_to: "unity"
why: "Unity's MonoBehaviour/Rigidbody/FixedUpdate model is a different engine; C# alone doesn't make it Godot."
- prompt: "Set up an Unreal Engine character with a Blueprint jump and a C++ movement component."
route_to: "unreal"
why: "Unreal Blueprint/UE C++ is a separate engine skill."
- prompt: "Write a .gdshader that does a dissolve effect with a noise texture and an edge glow."
why: "Shader authoring in .gdshader/visual shaders is delegated to gamedev-shaders, not GDScript gameplay code."
route_to: "gamedev-shaders"
- prompt: "Build a godot-cpp GDExtension purely as a CMake project and set up the compiler toolchain and SCons/CMake flags."
route_to: "cpp"
why: "The native C++ build/tooling side is cpp; this skill only points at GDExtension from the gameplay side."
- prompt: "Design the core game loop and progression economy for my roguelike before I build anything."
route_to: "game-design"
why: "Mechanics/loop/feel design precedes scripting and belongs to game-design."
- prompt: "Implement client-side prediction and server reconciliation for my Godot multiplayer shooter's netcode."
route_to: "gamedev-multiplayer"
why: "Deep netcode/RPC/synchronizer work is the multiplayer sibling; this skill stops at single-player node/signal basics."
capability:
- scenario: "Author a Godot 4.x 2D platformer player: a typed CharacterBody2D with gravity, run, and a floor-only jump, that emits a signal when it dies, plus the equivalent C# version."
must_include:
- "extends CharacterBody2D and sets the `velocity` property, then calls `move_and_slide()` with NO arguments (not move_and_slide(velocity, ...))"
- "Applies gravity via get_gravity() * delta (or a project-settings gravity) scaled by delta, inside _physics_process, and does not multiply the velocity passed to move_and_slide by delta again"
- "Uses gravity/jump only when appropriate with is_on_floor(), and reads input via Input.get_axis / Input.is_action_just_pressed"
- "Declares a signal (e.g. `signal died`) and emits it with `died.emit()`, never emit_signal string form as the primary API"
- "Is statically typed: typed params (delta: float), typed vars (:= / : Type), and a -> void / typed return where relevant"
- "Uses @export for tunables (speed, jump_velocity) and @onready + $ or %UniqueName for node refs — no onready/export without @, no yield, no .instance()"
- "C# version uses `public partial class ... : CharacterBody2D`, `_PhysicsProcess(double delta)` calling `base` where a base defines it, `[Export]`, `[Signal] ...EventHandler`, `EmitSignal(SignalName....)`, sets `Velocity` then `MoveAndSlide()`"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |