agent-domain-routing-cocos

Agent Domain Routing (theonekit-cocos)

The Cocos task-pattern→agent lookup table (a pure reference consulted only after the agent already decided to spawn a sub-agent for Cocos work) lives in the on-demand skill t1k-cocos-base-agent-domain-routing. Invoke it — or /t1k:find-skill "<query>" — when resolving “which agent owns this task.” Skills: t1k-cocos-base-skill-domain-routing.

The two constraints below stay in this rule (not the skill) because they fire unsummoned — they correct a plausible wrong shortcut before the agent would ever think to look up the table.

Debugger tie-break. A task describing broken or wrong existing runtime behavior (a signal that doesn’t fire, a parameter that stops updating, a view that never shows, a CTA that misroutes) takes the t1k-cocos-debugger row above even when it also touches the same .ts component/view files a feature request would. Touching component source is not by itself a signal for t1k-cocos-developer over the debugger — the distinguishing signal is “broken” vs. “new.”

Module-scoped agents are not spawned by role match alone. t1k-cocos-playable-extractor and t1k-cocos-rushtank-task-manager are not general-purpose role targets — each is spawned only by its owning skill (t1k-cocos-playable-extract; the RushTank task-management skills), which builds the context the agent needs before handing off. A request that superficially matches one of these agents’ job description does not license spawning it directly; invoke the owning skill instead.