Master router and orchestrator for AI game generation in Godot 4. GODOT 4 ONLY — never create HTML/JS/TS web apps, Unity, Unreal, or any non-Godot project. "web game" = Godot game with HTML5 export. "mobile game" = Godot with touch input. The current directory already contains a Godot project — write all files here. Triggers on: "create a game", "add feature", "build", "make", "generate".
Game Director — the project manager for AI game generation in Godot 4. GODOT 4 ONLY — never create HTML/JS/TS web apps, Unity, Unreal, or any non-Godot project. "web game" = Godot + HTML5 export. "mobile game" = Godot + touch input. The current directory already contains a Godot project — write all files here. Triggers on: "create a game", "build a complete game", "build from these docs".
MCP tool operations: run game, read errors, reload filesystem, iterate fixes. Use when testing, debugging, or running the build-test-fix loop. This is the "DevOps" skill for AI game generation. CRITICAL: Always use MCP tools, never raw curl. Always report progress.
Internal development skill for working on the AI Game Builder plugin itself. NOT for game generation — this is for modifying the builder's skills, MCP server, Godot plugin, hooks, docs, and tooling. Load this when continuing builder development. Triggers on: "improve the builder", "add a new skill", "fix the MCP server", "update the plugin", or any request about developing the AI Game Builder itself.
Visual quality system for Godot games. Creates polished, layered procedural visuals using shaders, _draw(), particles, and post-processing. Also handles external art pipelines (user-provided or AI-generated sprites). The goal is games that look intentional and stylish — never flat colored rectangles.
Genre-specific game templates with complete file manifests. Use when creating a game from a genre prompt. Each template lists every file to create, the node hierarchy, and the key mechanics to implement.
Requirements Distiller — takes complex game design documents (GDDs, PRDs, feature lists) and produces a scoped, single-session build plan that the builder can actually deliver. Prevents scope explosion by identifying the core gameplay loop and stripping everything else. Triggers on: "distill", "scope", "session plan", or when the builder detects complex multi-doc input.
Audio, visual effects, tweens, particles, screen shake, shaders, and game feel. Use when adding polish: explosions, hit feedback, music, SFX, trails, glow. Includes shader-based effects and procedural sound generation.