Dispatcher

Read the shared contract once. Interpret meaning, not literal keyword hits. Traditional and simplified Chinese share intents. Preserve the user's language.

Resolve before loading

Inspect current code/configuration. Explicit choices outrank existing settings, which outrank the seeds below. Prioritize the reported blocker over broad genre words. Do not silently switch an existing engine or ask for facts already supplied.

Use at most three specialized skills (including assets/2D) plus one necessary engine per phase. Deduplicate equivalent owners; record remaining work in DEFER and continue phase by phase. A linked skill is loaded only when its subject is needed, not recursively.

Each pair names a skill and its own mode. select means resolve from evidence or one consequential question; existing means preserve its current mode; n/a means no selector. These are routing directives, never game configuration values. Replace unresolved directives before implementation. Never invent a column to fill the output.

ENGINE is none for design-only work, unknown when unresolved, or the actual adapter. custom is a real custom runtime, not a guess. For uncovered intents, look up paths in ../catalog.json, inspect candidate descriptions, then load only matching bodies. The six engineering-core selectors and optional dependencies are scoped by ../engineering-registry.json; the registry narrows ownership but does not make select a gameplay mode. Studio names route through studio-columns only when the design direction is unresolved; release that picker before a three-discipline implementation phase.

Output

USE:
- <skill> / <resolved column or n/a>
ENGINE: <none|unknown|custom|threejs|pixijs|phaser|cocos|godot|unity|unreal>
ASK: <one necessary question or empty>
DEFER: <remaining phases or empty>

Then do the requested work. Do not dump the catalog. A missing tool means blocked/not-run, not success.

Routing seeds

These are examples, not permission to overwrite a chosen mode. Match semantic equivalents in all supported languages.

Generic does not mean an automatic franchise preset. Debug-assisted footage is never a natural clear. Choose a declared gameplay-capture mode from evidence, not the word "trailer" alone; disclose altered unlocks separately.

Acceptance

Given a request with an explicit engine or mode, preserve it unless evidence makes it impossible. For ambiguous engineering-core requests, route to the matching registered owner with select, then resolve that directive before implementation. Never emit more than three specialized skills plus one engine in one phase; overflow goes to DEFER. Test explicit-choice precedence, overlapping signals, uncovered-catalog fallback and all six engineering-core seeds. A routing-table match is deterministic contract evidence, not proof of LLM intent classification accuracy.

Fixture preparation

When tests need external art/audio/effects, use open-asset-fixture in the preparation phase before generation. Preserve explicit asset requirements and already-authorized fixtures. It consumes one specialized slot; defer it to a separate phase rather than expanding the active set. Pure logic tests do not need an art download.

Foot slip after a rig/clip swap routes to character-rig first; slip caused by slope/support contact stays with ik-foot-locking. A black screen alone is not proof of context loss: diagnose the event/resource failure before choosing recovery.