Master Router — Game-Development Skill Dispatcher

The entry point for game-development work. It fingerprints the project to pick one engine,
classifies the task from the request, names the minimal set of specialized skills, and tells
you to read them before acting. It dispatches and composes — it does not re-teach engine APIs.

When to use

• Use at the start of any game-development request — building or debugging a game, level,
  player, enemy, shader, UI, save system, multiplayer, input, audio, AI, dialogue, or procedural
  content — to decide which skill(s) to load.
• Use when the user names an engine or genre, says "make a game", or asks "which skill should I
  use?".

When not to use: once the right skill is loaded and the task is squarely inside it, work
from that skill — don't re-run the router every turn. Re-route only when the task pivots to a
new engine or concern (router step 6).

Routing algorithm

1. Detect engine — project fingerprint → at most one engine skill set (or "unknown"). §1.
2. Classify task — phrasing → discipline(s) + at most one genre + workflow(s). §2.
3. Resolve — the minimal set: engine skill(s) + discipline(s) + genre + workflow(s). §3.
4. Read (disclosure) — open only the chosen SKILL.md bodies; references/ only on demand. §4.
5. Compose — order: engine fundamentals → discipline concept → genre glue → workflow. §5.
6. Fallback — engine unknown or no skill fits → ask or default to Godot; state any gap. §6.