claude-code-gamedev

Workflow orchestration skill for building game prototypes with Claude Code + Godot MCP. Activate this skill whenever starting a new game project, resuming game development work, planning game mechanics or features, or the user says anything like "build a game", "create a game", "make a platformer", "make an RPG", "let's build a shooter", "start a new Godot project". Also activate when discussing game architecture, scoping a prototype, or choosing between game genres. This is the top-level conductor — it coordinates the entire process from concept to playable prototype. Even if you know how to build games, use this skill: it codifies lessons from real sessions that prevent hours wasted on silent MCP failures, wrong sprite layouts, and missing collision shapes.

GDScript 4.x language skill for writing correct, idiomatic, type-safe GDScript code in Godot Engine projects. Activate this skill whenever writing, editing, reviewing, or debugging ANY .gd file, implementing game systems in GDScript, discussing GDScript syntax or patterns, or encountering GDScript runtime errors. Even simple scripts benefit from correct style and type safety — if the task involves GDScript in any way, use this skill. Do not skip this for "quick" scripts; most GDScript bugs come from skipping conventions on "simple" code.

Operational guide for using Godot MCP (godot-mcp) tools correctly. Activate this skill whenever calling ANY Godot MCP tool (create_scene, add_node, load_sprite, run_project, etc.), setting up a Godot project for MCP use, building scenes programmatically, or running the debug loop. Also activate when discussing MCP capabilities/limitations or when a subagent is delegated to do MCP scene-building work. Without this skill, Claude will hit silent failures — Vector2 properties dropped, load_sprite errors on un-imported assets, orphan debug processes. This skill prevents all of them.

File format skill for safely editing Godot .tscn and .tres scene/resource files. Activate this skill whenever reading, writing, or editing ANY .tscn or .tres file — creating scenes from scratch, attaching scripts to nodes, adding sub-resources (collision shapes, materials, animations), setting complex properties (Vector2, Color, Rect2, Transform2D), instancing sub-scenes, adding signal connections, fixing merge conflicts, or patching scenes after MCP operations. Without this skill, .tscn edits risk silent corruption — scenes load but behave wrong, or Godot re-saves them differently. Even small edits need correct section ordering, ID uniqueness, and reference syntax. If the task touches a .tscn or .tres file in any way, use this skill.

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.