Skip to main content
skill CX Codex

godot-composition — Claude Code skill: component architecture

Tells your agent to build Godot entities from components instead of inheritance chains, with ready-made GDScript files for health, hitboxes and movement.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-composition -a claude-code
Open on GitHub

What godot-composition does

The skill pushes a "Has-A" model: a player, enemy or weapon is a root orchestrator node holding specialised child components. That root script carries no logic of its own — it passes data between children. Shipped scripts cover health_component.gd, hit_box_component.gd, hurt_box_component.gd, velocity_component.gd, interaction_component.gd, follower_component.gd, state_component_vsm.gd, status_effect_component.gd and visual_sync_component.gd.

Wiring goes through typed @export slots or %UniqueNames in the scene. Reaching for $ or get_node() to grab a component is off the table, because rearranging the tree breaks those paths. A component stays selfish: it never references its owner, talking upward with signals and receiving calls downward. The skill marks composition_root_init.gd as the mandatory first read.

A decision table sorts the grey areas. Gameplay behaviours belong in components, cross-scene services such as audio or saves go to Autoload, and inheritance is reserved for genuine engine-class specialisation. You need Godot and GDScript — this is a set of rules plus scripts, not a library you import into a project.

What it helps with

  • split a player controller into separate components
  • reuse health logic across players and enemies
  • wire hitboxes and damage areas without hardcoded scene paths
  • build a state machine out of child nodes
  • keep sprite flipping out of movement logic

Example prompts for the agent

  • Refactor player.gd into components following godot-composition
  • Give this enemy shooting through a separate component, no inheritance
  • Check my scene: components should be wired with @export, not $

How to install godot-composition

1Skills CLI (Vercel)

npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-composition -a claude-code

2Manually: put the files in place

~/.claude/skills/godot-composition/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/godot-composition/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about godot-composition

How do I install godot-composition in Claude?

Run npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-composition -a claude-code. The skill file lands at ~/.claude/skills/godot-composition/SKILL.md.

What does godot-composition do?

It gives your agent architectural rules for Godot games: entities are assembled from components, and the root script only orchestrates them. Bundled scripts handle health, hitboxes, movement, interaction and states.

How is composition different from inheritance here?

Inheritance is kept for engine-class specialisation with a shared lifecycle. Adding a feature such as shooting or health through a parent chain is explicitly disallowed — that becomes its own component.

Similar skills

Everything for Game dev and 3D: Unity, Unreal, Godot, Blender →

From the same set50

godot-gdscript-mastery Guides coding agents through GDScript pitfalls, enforcing static typing and safe node lifecycle patterns in Godot. CX Codex +1 612installs godot-save-load-systems Save and load blueprints for Godot covering JSON and binary serialization, version migration, and rolling backups. Keeps game state handling consistent. CX Codex +1 595installs godot-testing-patterns Provides testing decision trees and GdUnit4 templates for Godot. Guides developers through unit tests, headless CI runs, frame stepping, and network mocks. CX Codex +1 585installs godot-3d-world-building A skill for building 3D levels in Godot: GridMap with MeshLibrary, CSG greyboxing, occlusion and chunk streaming. Useful once a prototype has to become a playable scene. CX Codex +1 536installs godot-2d-physics Guides coding agents through Godot 2D physics architecture. Prevents common pitfalls across collision layers, raycasts, and custom space queries. CX Codex +1 516installs godot-ui-containers Provides blueprints and rules for responsive Godot UI using Container nodes. Useful when building adaptive menus, shop grids, or virtualized scroll lists. CX Codex +1 507installs godot-input-handling A skill that gives your coding agent ready patterns for Godot input: InputMap actions, gamepads, rebinding, deadzones and input buffering. CX Codex +1 509installs godot-combat-system A skill that tells the agent how to build hitboxes, damage and i-frames in Godot. Useful for action games, RPGs and fighters. CX Codex +1 507installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor