agent-domain-routing-designer

Agent Domain Routing (theonekit-designer)

The game-design task-pattern→agent lookup table (moved 2026-08-31, context-budget lever — pure reference consulted only after the agent already decided to spawn a sub-agent for game-design work) now lives in the on-demand skill t1k-designer-base-agent-domain-routing. Invoke it — or /t1k:find-skill "<query>" — when resolving “which agent owns this design task.” Role keys: .claude/t1k-routing-designer.json. Skills: t1k-designer-base-skill-domain-routing.

Designer sits at registry priority 50 — below engine kits at 90 — so in a session with an engine kit installed alongside, designer’s generic-core-role overrides (implementer, reviewer, …) are shadowed by the engine kit’s. The routing skill’s rows (which are named per design task, not per role) still apply; read them by task. There is no unsummoned tie-break constraint to keep here — with three agents and a small role table, the only always-fires rule worth stating is the one already enforced by rules/skill-domain-routing-designer.md: design artifacts get design-perspective agents, never t1k-code-reviewer.