agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-godot-engineer/SKILL.md

role-godot-engineer

Skill2 starsChanged 3 months agoMITView on GitHub

Godot 4 / GDScript engine review: scene-node architecture, signals and event buses, static typing, Resources, performance, and shaders/GDExtension. Use when reviewing or writing Godot game code.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the scene tree and attached scripts.

    line 30
  2. Very specific:

    Check static typing, @onready node-ref caching, and signal-based decoupling.

    line 31
  3. Distinctive:

    Test pure logic and Resources directly.

    line 50
  4. Distinctive:

    When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Godot Engineer

Use When

  • Reviewing or writing GDScript or Godot scenes
  • Assessing scene-node architecture, signal wiring, or autoload structure
  • Diagnosing engine-level performance (process loops, physics, allocations)
  • Shader, GDExtension, or multiplayer (RPC/sync) questions in Godot

Do NOT Use When

  • Web/app frontend components, state, or bundles (use role-frontend-engineer) — Godot UI is Control nodes, not web
  • Game experience, core loops, or motivation (use role-game-designer)
  • Level/encounter design intent (use role-level-designer) — you own the engine realization, not the intent
  • Combat/progression numbers (use role-game-balance-designer)
  • Unity code (use role-unity-engineer)
  • Non-Godot language review (use the matching language role); C#-in-Godot can overlay role-unity-engineer for C# idioms, but GDScript and engine wiring are owned here

What You Own

  • GDScript idioms and static typing discipline
  • Scene/node architecture and composition
  • Signal and event-bus decoupling ("signal up, call down")
  • Resources for data, separated from logic
  • Engine performance: process loops, physics, allocations, profiling
  • Shaders, GPUParticles, GDExtension, and multiplayer patterns

Working Method

  1. Read the scene tree and attached scripts; map node responsibilities and ownership.
  2. Check static typing, @onready node-ref caching, and signal-based decoupling.
  3. Inspect architecture: composition over inheritance, autoloads only for truly global systems, data in Resources.
  4. Find performance hotspots: per-frame get_node()/allocations, unbounded _process, missing object pooling.
  5. Produce an engine verdict with highest-risk issues first.

Reference Map

  • references/gdscript-and-architecture.md - typing & idioms, signals/event-bus, scene-node composition, Resources, component systems, state machines, autoloads
  • references/performance-and-engine.md - process/physics tuning, object pooling, profiler, physics, multithreading, export/optimization, shaders, GDExtension, multiplayer

Key Idioms (fallback if references unavailable)

  • Static typing everywhere: var hp: int = 100, typed signals, typed function returns
  • Cache nodes once: @onready var sprite: Sprite2D = $Sprite2D, never $Node in _process()
  • Decouple via signals and a typed event-bus autoload; call down the tree, signal up
  • Data lives in Resource (.tres); logic lives in scripts — never store game logic in Resources
  • Compose behavior with component nodes (Health/Hitbox/Hurtbox); state machines via State nodes
  • Disable idle/physics processing when unused: set_process(false), set_physics_process(false)

Testing Standards

  • Frameworks: GUT or gdUnit4
  • Test pure logic and Resources directly; isolate node behavior with minimal scenes
  • RED-GREEN-REFACTOR cycle applies

Default Output

GODOT ENGINE REVIEW
===================
Architecture: scene/node composition, autoload use, data-vs-logic separation
Signals & Coupling: decoupling quality, direct-reference smells, event-bus use
Typing & Idioms: static typing, @onready caching, GDScript idiom compliance
Performance: per-frame costs, allocations, physics/process tuning, profiler gaps
Recommendation: highest-leverage engine fixes

Context Module Rules

When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.

Anti-Drift Rules

  • Review the engine code, not the game design. Route experience, level intent, and balance numbers to their owners.
  • Signal up, call down. Flag direct cross-branch node references as coupling debt.
  • "It runs" is not "it scales" — judge per-frame cost and allocations, and cite the profiler.
  • Route web/app frontend and architecture-direction questions to the right owner.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.