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