Skip to content

agent-domain-routing-cocos

The Cocos task→agent lookup table lives in the on-demand skill t1k-cocos-base-agent-domain-routing; invoke it, or /t1k:find-skill "<query>", to resolve “which agent owns this task.” The constraints below stay here: they fire unsummoned, correcting a wrong shortcut before the table would be consulted. Full agent list per constraint: docs/agent-domain-routing-cocos.md.

Debugger tie-break. A task describing broken/wrong existing behaviour takes t1k-cocos-base-debugger even when it touches the same files a feature request would; the signal is “broken” vs. “new”.

Module-scoped agents are not spawned by role match alone. An agent like t1k-cocos-playable-extractor is spawned only by its owning skill.

Verification is the exception, deliberately. t1k-gamedev-playable-runtime-verifier carries role playable-verifier in t1k-routing-gamedev-playable.json (gamedev playable) and IS a legitimate role target: a verification hop has no other way in.

Cocos lanes do NOT default to t1k-fullstack-developer (engine-agnostic fallback only). “Implement” with no narrower row is t1k-cocos-base-feature-implementer (code only) or t1k-cocos-base-developer (scene/prefab/editor wiring); an engine-free package is t1k-cocos-base-package-developer. Copying/importing original assets and placeholder ledgers is t1k-cocos-base-asset-porter; level/config/localization JSON is t1k-cocos-base-data-author; authoring tests is t1k-cocos-base-test-writer; read-only mapping is t1k-gamedev-architecture-system-mapper (theonekit-gamedev). Prefab/scene writes are never an asset-porter job (editor MCP only). Row-by-row table and tiers: the routing skill and docs/agent-tier-map.md.

Feature work is one agent: the developer writes the TS AND performs its editor writes. t1k-cocos-base-developer holds the same mcp__cocos-creator__* / mcp__cocos-mcp-server__* grant as the operator and is bound to the save → reimport → read-from-disk protocol (t1k-cocos-base-editor-mcp-truth) plus the editor-preview gate before any Jenkins build. Never split a feature into a code lane and an editor lane. t1k-cocos-base-editor-operator stays for editor-only jobs (no TS change) and for repair. t1k-cocos-playable-feel-developer (PolishKit wiring needs prefab @property refs) holds the same grant and protocol.