t1k:cocos:base:agent-domain-routing
| Field | Value |
|---|---|
| Module | base |
| Version | 4.51.9 |
| 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 theonekit-core/.claude/modules/t1k-orchestration/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.
Mirrors theonekit-unity’s
t1k-unity-base-agent-domain-routing(moved out of a rule 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 build.sizeBudgetMB budget / parameter system / SDK compat / single-scene constraint — no code written | t1k-cocos-base-brainstormer |
Diagnosing a runtime issue to root cause — parameter not updating, signal not firing, SDK/CTA failure, view not showing, TypeScript error, broken layout. Diagnosis only: the fix goes to t1k-cocos-base-developer (or t1k-cocos-base-editor-operator for an editor-only repair) | t1k-cocos-base-debugger |
| Implementing a feature — new parameter, view, SDK/CTA wiring, game-flow state, PLAGameFoundation integration — including that feature’s scene/prefab/component writes through the editor MCP | t1k-cocos-base-developer |
Implementing code only (TypeScript: services, signals, game-flow state, SDK/CTA glue), no scene/prefab/@property writes — the implement default when no narrower row fits | t1k-cocos-base-feature-implementer (role feature-implementer; native, code-only) |
Porting a Unity/uGUI screen or prefab to Cocos — layout, CanvasGroup, LayoutGroup, RectMask2D fidelity (t1k-cocos-base-apk-port § ugui-to-cocos-fidelity); copying its sprites/atlases with .meta is the asset-porter row | t1k-cocos-base-developer |
Authoring or porting a .effect/.mtl shader — hit flash, toon, render queue; a Unity .shader goes through t1k-cocos-base-unity-shader-port first, then t1k-cocos-base-effect-authoring. A broken shader is the debugger row | t1k-cocos-base-developer |
An ENGINE-FREE TS package (never imports cc) in a pnpm workspace | t1k-cocos-base-package-developer |
Importing/copying original or ripped assets with their .meta, promoting _Incoming/, editor-extension builder scripts, the placeholder ledger (never prefab/scene authoring; cheap-routed) | t1k-cocos-base-asset-porter (role asset-porter) |
Renaming the CocosTemplate/ folder to the game’s name and the pins that go stale with it (t1k-cocos-base-cleanroom-adapter) | t1k-cocos-base-asset-porter (role asset-porter) |
| Level/config/localization JSON, resource tables, parameter defaults, design-doc-to-data parity (cheap-routed) | t1k-cocos-base-data-author (role data-author) |
| Authoring Vitest tests for plain-TS logic and manual Editor checklists, each proven RED (cheap-routed; verifying a finished feature is the tester row) | t1k-cocos-base-test-writer (role test-writer) |
Read-only mapping — systems vs @playablelabs/*, overlap scan, ownership table, no edits (cheap-routed) | t1k-gamedev-architecture-system-mapper (theonekit-gamedev architecture; Cocos scan targets come from x-knowledge / x-mapping in t1k-cocos-base-gamedev-adapter) |
| Editor bridge or checkout suspected wrong, not merely closed — MCP on the wrong project, dead port, empty submodule | t1k-cocos-base-editor-doctor |
Running a stdlib-contribution on an accepted candidate (Steps 3-10 of t1k-cocos-base-stdlib-contribute: port, scaffold, verify, review, open the PR); spawned by its owning skill | t1k-cocos-playable-stdlib-contributor (module: playable) |
| Visual-fidelity judgment on a playable — pre-implementation design brief or post-build screenshot review (advisory, never edits) | t1k-gamedev-playable-visual-director (module: playable) |
Editor-only job with no TypeScript change, or repair of a broken scene/prefab — wiring an @property, adding/removing a component, node hierarchy or layer change, reference assignment, asset reimport, reading back what the editor holds | t1k-cocos-base-editor-operator |
Size/performance optimization — bundle size reduction, asset audit, import pruning, texture compression, staying inside the build.sizeBudgetMB budget | t1k-cocos-base-optimizer |
| Pre-PR code review — parameter wiring, SDK compatibility, signal flow, size impact, pattern compliance (reads and reports, never fixes) | t1k-cocos-base-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-base-tester |
| Read-only runtime lifecycle validation end-to-end — loading, FTUE, gameplay, win/lose, end card, CTA redirect | t1k-cocos-base-validator |
Driving a built playable headless in Chrome to get a runtime verdict — exit code, console errors/exceptions, whether the CTA actually fired, numeric diffPercent against a baseline; reports what the tool measured, never fixes and never judges feel | t1k-gamedev-playable-runtime-verifier (theonekit-gamedev module playable — only when installed; role playable-verifier in t1k-routing-gamedev-playable.json) |
Reverse-engineering a competitor playable HTML bundle into gameplay/code-structure/Cocos-rebuild docs — always spawned by its owning skill t1k-gamedev-playable-extract, never by a direct role match | t1k-cocos-playable-extractor (module: playable) |
Adversarially gating one harvest candidate’s scaffolded-package diff at S8 of the harvest pipeline — reads the candidate record, purity/equivalence/match evidence and the worktree diff, returns one JSON verdict (APPROVE | REVISE | REJECT); always spawned by its owning skill t1k-cocos-playable-stdlib-harvest, never by a direct role match | t1k-cocos-base-stdlib-gatekeeper (module: base) |
Closing a PLA stdlib retrofit — runs every mechanical gate over the whole repo (dead code, cc-thickness, hardcode, source-scan, portability, tsc, tests, adoption), then grades SOLID/patterns against docs/system-design.md; returns one JSON verdict PASS | REVISE with rubric-id findings. Spawned by t1k-cocos-playable-pla-retrofit at stage B9, or directly when the caller wants a repo-level verdict; never for a one-file diff | t1k-cocos-playable-pla-retrofit-reviewer (module: playable — identity role) |
Pick by task shape, not by who is nearest
Section titled “Pick by task shape, not by who is nearest”Cocos lanes do NOT default to t1k-fullstack-developer (engine-agnostic fallback only). It stays correct only for steps with no engine role at all, such as Plane bulk writes in t1k-cocos-playable-pipeline. Cocos code is feature-implementer / developer / package-developer; asset import is asset-porter; data is data-author; tests are test-writer; mapping is t1k-gamedev-architecture-system-mapper. Tiers, routable: flags and turn budgets: docs/agent-tier-map.md.
- Mechanical or code-only work goes to a hop agent, one deliverable each, no editor tools. A
routable: truehop needsworktree: <abs>alone on its own line and a validatedcontract:line; do not assume a hop is routed. - A lead only decides and briefs. A phase spanning TS, data and tests is split into those hops (in parallel when files are disjoint); editor-MCP work (scene, prefab,
@property) stays witht1k-cocos-base-developer. - Prefab and scene writes are never a cheap hop. They need the
cocos-creatorMCP, which the router does not forward; the asset-porter only places files and writes ledger rows.
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), the “module-scoped agents are never spawned by role match alone” constraint, and the editor-write rule (feature work is one agent: the developer writes TS and performs its editor writes; the operator is for editor-only jobs and repair) live in .claude/modules/base/rules/agent-domain-routing-cocos.md — read that first; it is what tells you when to consult this table.