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 |
references/gdscript-style.md
View on GitHub# GDScript style & formatting cheat-sheet (Godot 4.x)
Mirrors the official GDScript style guide. When in doubt, run the editor's built-in formatter
(Ctrl/Cmd+Shift+I) and `gdformat` (from `gdtoolkit`) in CI.
## Naming
| Thing | Case | Example |
| --- | --- | --- |
| File (script/scene) | `snake_case` | `player_controller.gd`, `main_menu.tscn` |
| `class_name` / type | `PascalCase` | `class_name EnemyStats` |
| Node name in tree | `PascalCase` | `HealthBar`, `AttackTimer` |
| Variable / function | `snake_case` | `var max_health`, `func take_damage()` |
| Signal | `snake_case`, past tense | `signal health_depleted` |
| Constant | `CONSTANT_CASE` | `const MAX_SPEED := 400.0` |
| Enum type / members | `PascalCase` / `CONSTANT_CASE` | `enum State { IDLE, RUN }` |
| Private (convention) | leading underscore | `var _internal_timer` |
| Virtual/lifecycle | leading underscore | `_ready`, `_process`, `_on_body_entered` |
## Formatting
- **Tabs** for indentation (not spaces). Editor default.
- Lines **< 100 columns**.
- One space around binary operators (`a + b`, `x := 1`), none inside call parens.
- Two blank lines between functions at top level; one inside classes as needed.
- Prefer `:=` (inferred) when the RHS makes the type obvious; `: Type =` when it does not.
## Typed by default
```gdscript
var speed: float = 300.0 # explicit annotation
var dir := Vector2.ZERO # inferred
var slots: Array[Item] = [] # typed collection
const GRAVITY := 980.0
func heal(amount: int) -> void: # typed params AND return
_health = mini(_health + amount, _max_health)
func find_target() -> Node2D: # return type declared
return get_tree().get_first_node_in_group("player")
```
- Declare `-> void` on functions that return nothing; declare the real type otherwise.
- Use `as` for safe downcasts: `var e := body as Enemy` → `null` on mismatch (no crash).
- Avoid untyped `var x` and `Variant` params — they disable the compiler's checks and the VM's
typed fast paths.
## Script layout order (recommended top-to-bottom)
1. `@tool` (if any) — must be the very first line.
2. `class_name` then `extends` (or `extends` alone).
3. `## docstring` comment.
4. `signal` declarations.
5. `enum` / `const`.
6. `@export` vars, then plain member vars, then `@onready` vars.
7. Built-in virtuals: `_init`, `_ready`, `_process`, `_physics_process`, `_input`, …
8. Public methods, then private (`_underscore`) methods, then signal handlers (`_on_*`).
```gdscript
@tool
class_name Turret extends Node2D
## Auto-aiming turret; @export the fire rate in the inspector.
signal fired(at: Vector2)
const MAX_RANGE := 600.0
enum Mode { IDLE, TRACKING }
@export var fire_rate := 2.0
var _cooldown := 0.0
@onready var muzzle: Marker2D = %Muzzle
func _physics_process(delta: float) -> void:
_cooldown = maxf(_cooldown - delta, 0.0)
func _on_area_entered(_area: Area2D) -> void:
pass
```
## Common built-in math helpers (Godot 4 names)
`absf/absi`, `minf/mini`, `maxf/maxi`, `clampf/clampi`, `snappedf`, `lerpf`, `move_toward`,
`deg_to_rad` / `rad_to_deg`, `randf_range`, `randi_range`. The unsuffixed `abs/min/max/clamp` still
work on Variants but the typed suffixed forms are faster and clearer.
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 |