t1k:cocos:base:agent-domain-routing
| Field | Value |
|---|---|
| Module | base |
| Version | 3.3.2 |
| Effort | low |
| Tools | — |
Keywords: agent domain, agent for, agent lookup, agent routing, cocos agent, discover agent, playable agent, route to agent, spawn agent, which agent
How to invoke
Section titled “How to invoke”/t1k:cocos:base:agent-domain-routingAgent Domain Routing (theonekit-cocos)
Section titled “Agent Domain Routing (theonekit-cocos)”Cocos rows for core rules/orchestration-rules.md § “Task-Type → Agent Routing”. Skills: t1k-cocos-base-skill-domain-routing. Behavioral constraints that fire before this table would be consulted: .claude/modules/base/rules/agent-domain-routing-cocos.md.
Added 2026-08-31, mirroring theonekit-unity’s
t1k-unity-base-agent-domain-routing(moved out of a rule on 2026-08-24 as a context-budget lever — this table is consulted only after the agent has already decided to spawn a sub-agent for Cocos work)./t1k:find-skillalso resolves this table by keyword.
| Task pattern | Agent |
|---|---|
| Ideating a mechanic or technical approach, ranking options against the 2-5MB budget / parameter system / SDK compat / single-scene constraint — no code written | t1k-cocos-brainstormer |
| Diagnosing AND fixing a runtime issue — parameter not updating, signal not firing, SDK/CTA failure, view not showing, TypeScript error, broken layout | t1k-cocos-debugger |
| Implementing a feature — new parameter, view, SDK/CTA wiring, game-flow state, PLAGameFoundation integration | t1k-cocos-developer |
| Size/performance optimization — bundle size reduction, asset audit, import pruning, texture compression, staying inside the 2-5MB budget | t1k-cocos-optimizer |
| Pre-PR code review — parameter wiring, SDK compatibility, signal flow, size impact, pattern compliance (reads and reports, never fixes) | t1k-cocos-reviewer |
| Static verification that an implementation is wired correctly (parameter/view/signal/SDK), plus the manual Editor checklist for the engine-coupled steps that can’t be automated | t1k-cocos-tester |
| Read-only runtime lifecycle validation end-to-end — loading, FTUE, gameplay, win/lose, end card, CTA redirect | t1k-cocos-validator |
Reverse-engineering a competitor playable HTML bundle into gameplay/code-structure/Cocos-rebuild docs — always spawned by its owning skill t1k-cocos-playable-extract, never by a direct role match | t1k-cocos-playable-extractor (module: playable) |
Listing/fetching/creating/updating/commenting on RushTank tasks via the configured provider — always spawned by its owning task-management skills (t1k-cocos-rushtank-task-framework, t1k-cocos-rushtank-plan-tasks), never by a direct role match | t1k-cocos-rushtank-task-manager (module: rushtank) |
Related
Section titled “Related”The debugger tie-break (a task naming broken/wrong existing behavior takes the debugger row even when it also touches component/view source files) and the “module-scoped agents are never spawned by role match alone” constraint live in .claude/modules/base/rules/agent-domain-routing-cocos.md — read that first; it is what tells you when to consult this table.