What problem does it solve? Game-development requests span many engines and topics, and loading the wrong or too many skills wastes context and produces mismatched guidance. This Skill fingerprints the project to detect the engine, classifies the task, and selects the minimal set of specialized skills to read before acting. ## Core Features & Use Cases - Engine Detection: Identifies exactly one engine from project files such as project.godot, *.uproject, Assets/ plus ProjectSettings, package.json dependencies, Cargo.toml, or Roblox place files, covering Godot, Unity, Unreal, Bevy, Phaser, PixiJS, three.js, LÖVE, pygame, and Roblox. - Task Classification and Routing: Maps request phrasing and file signals to disciplines (game-ai, save-systems, shader-programming, game-feel, camera-systems, performance-optimization, and more), genres (platformer, roguelike, RPG, FPS, tower-defense, card game, visual novel, survival-crafting, puzzle), and workflows (game-jam, prototype-fast, steam-publish, itch-publish). - Progressive Disclosure and Fallbacks: Reads only the chosen skill bodies, composes them in a defined order, handles unknown engines by asking one targeted question or defaulting to Godot, and states binding gaps honestly instead of fabricating skills. - Use Case: A user says "add a double jump to my Godot player"; the router detects Godot from project.godot and loads godot-2d-movement plus the platformer genre skill before any code is written. ## Quick Start Use the router skill to decide which game-development skills apply to my request before writing any code.
