What problem does it solve? Developers working on the AI Game Builder itself need a single reference covering its three-layer architecture (Claude Code plugin, Node.js MCP server, Godot editor plugin) so they can safely add skills, MCP tools, hooks, and endpoints without breaking cross-component contracts. ## Core Features & Use Cases - Architecture Map: Documents the full file layout of skills, hooks, the MCP server (tools.js, godot-bridge.js, asset-generator.js), and the Godot editor plugin (http_bridge.gd, dock.gd, error_collector.gd). - Step-by-Step Dev Recipes: Provides procedures for adding MCP tools, new skills, hooks, asset generator entity types, and modifying the Director's 6-phase build protocol. - Conventions & Pitfalls: Enforces logging rules, error-gate behavior, checkpoint/build-state schema, commit style, and lessons learned such as project.godot fragility and SVG quality rules. - Use Case: When asked to "add a new MCP tool" or "fix the MCP server", load this skill to get the exact files to edit, dispatcher patterns, bridge endpoints, and documentation files to keep in sync. ## Quick Start Ask the AI to load the godot-dev skill and add a new MCP tool that reports the current Godot editor selection.