Skip to content

t1k:designer:base:agent-domain-routing

FieldValue
Modulebase
Version1.25.1
Effortlow
Tools—

Keywords: agent domain, agent for, agent lookup, agent routing, designer agent, discover agent, game design agent, route to agent, spawn agent, which agent

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

Game-design rows for core rules/orchestration-rules.md § “Task-Type → Agent Routing”. Role keys: .claude/t1k-routing-designer.json. Skills: t1k-designer-base-skill-domain-routing.

Moved out of .claude/rules/agent-domain-routing-designer.md on port-2026-08-31 (context-budget lever — this table is consulted only after the agent already decided to spawn a sub-agent for game-design work). Designer sits at registry priority 50 (below engine kits at 90); keep reading the per-row note below. /t1k:find-skill also resolves this table by keyword.

Designer’s three agents map onto generic core role names (implementer, reviewer, optimizer, debugger, brainstormer) that read as engineering roles but here mean game-design work. Read the rows below by the task, not the role name.

User wants to…

  • Create/update a Game Design Document, demo wiki page, docs/wiki/ or architecture wiki → t1k-designer-game-designer
  • Sync documentation with code constants (verify numbers against Editor//Runtime/), cross-reference audits → t1k-designer-game-designer
  • Author design data (CSV/JSON, balance tables, item data) as a design deliverable → t1k-designer-game-designer
  • Review a design doc for pillar coverage / content completeness → t1k-designer-game-designer

Production Oversight, Milestones & Balance Review

Section titled “Production Oversight, Milestones & Balance Review”

User wants to…

  • Check milestone readiness (alpha/beta/RC/gold gates), run a milestone gate audit → t1k-designer-game-producer
  • Coordinate playtest cycles / triage playtest feedback → t1k-designer-game-producer
  • Design a sprint focus (content vs feature vs polish vs bugfix) → t1k-designer-game-producer
  • Run a balance audit after stat changes (DPS/EHP/TTK, difficulty spikes) → t1k-designer-game-producer
  • Review economy/monetization: pricing tiers, rarity distribution, sink/faucet → t1k-designer-game-producer
  • Review production readiness / ship-gate / stakeholder-decision propagation → t1k-designer-game-producer

User wants to…

  • Brainstorm a new mechanic, feature, or system (with DOTS feasibility + balance impact) → t1k-designer-brainstormer
  • Explore economy / crafting / monetization concept space → t1k-designer-brainstormer
  • Review for tone, voice, pillar fidelity during multi-agent fan-out → t1k-designer-brainstormer
  • p50 shadowing: t1k-routing-designer.json is priority 50, below engine kits’ 90 — so a session in a Unity/designer project will NOT get designer’s implementer even though designer maps it; the engine kit’s role override wins. Rely on this table for the design task rows it names, and read the per-row agent list — do not assume any generic core role (implementer, reviewer, …) resolves to a designer agent when an engine kit is installed alongside.
  • Anti-pattern: spawning t1k-code-reviewer for design-doc review. Design artifacts get design-perspective agents per .claude/rules/agent-domain-routing-designer.md.
  • Peer boundary: production tracking (plans, tasks, docs coordination) belongs to core’s t1k-project-manager; only milestone oversight / sprint design / balance goes to t1k-designer-game-producer.