Skip to content

t1k:nakama:base-agent-domain-routing

FieldValue
Modulebase
Version1.8.0
Effortlow
Tools—

Keywords: agent domain, agent for, agent lookup, agent routing, discover agent, go agent, nakama agent, route to agent, spawn agent, which agent

/t1k:nakama:base-agent-domain-routing

Nakama/Go row for core rules/orchestration-rules.md § “Task-Type → Agent Routing”. Role keys, file globs and error-recovery mappings: .claude/t1k-routing-nakama.json. Rationale for this layer’s shape: .claude/modules/base/rules/agent-domain-routing-nakama.md.

Ported from theonekit-unity’s t1k-unity-base-agent-domain-routing (2026-08-31), which moved its table out of a flat rule into an on-demand skill on 2026-08-24 as a context-budget lever — a lookup table is consulted only after an agent has already decided to spawn a sub-agent, so it does not need to be always-loaded. Nakama currently ships exactly one agent, so this table has exactly one row; it is ported anyway for surface consistency across T1K kits, and so the layer is already in place if nakama grows more agents later.

Task patternAgent
Go runtime plugin code — RPC handlers (RegisterRpc), hooks, auth adapters, gRPC clients, mock endpoints; any file under modules/, internal/, pkg/, or matching *.go (per .claude/t1k-routing-nakama.json fileRouting)t1k-nakama-base-developer

t1k-nakama-base-developer is registered for all four roles this kit needs — implementer, debugger, tester, game-developer — so every Nakama/Go task routes to the same agent regardless of which role it’s playing. This table has one row because the kit has one agent, not because rows were collapsed for brevity: a debugging task and an implementation task both resolve here today. If nakama adds a second agent, split this row then; do not pre-split it now to look more substantial than the kit’s current agent roster actually is.

.claude/modules/base/rules/agent-domain-routing-nakama.md — the always-loaded pointer to this skill, and why it carries nothing beyond that pointer.