t1k:rn:base:agent-domain-routing
| Field | Value |
|---|---|
| Module | base |
| Version | 1.13.0 |
| Effort | low |
| Tools | — |
Keywords: agent domain, agent for, agent lookup, agent routing, discover agent, react native agent, rn agent, route to agent, spawn agent, which agent
How to invoke
Section titled “How to invoke”/t1k:rn:base:agent-domain-routingAgent Domain Routing (theonekit-rn)
Section titled “Agent Domain Routing (theonekit-rn)”React Native rows for core rules/orchestration-rules.md § “Task-Type → Agent Routing”. Role keys, file globs and error-recovery mappings: .claude/t1k-routing-rn.json and the performance overlay .claude/modules/performance/t1k-routing-performance.json. Skill discovery: .claude/rules/skill-domain-routing-rn.md.
Moved out of rules into this skill as a context-budget lever — this table is consulted only after the agent already decided to spawn a sub-agent for RN work. The tie-break and any unsummoned constraints that fire before an agent would otherwise pick the wrong specialist stay behind in the rule
t1k-rn-base-agent-domain-routing; only this table lives here./t1k:find-skillalso resolves this table by keyword.
| Task pattern | Agent |
|---|---|
Implement an Expo/RN feature, screen, component, or store — Expo Router, Zustand/MMKV/AsyncStorage, StyleSheet.create, memo/useCallback | t1k-rn-base-developer |
Jest unit tests, @testing-library/react-native component tests, Detox E2E | t1k-rn-base-tester |
Debug a crash, Metro error, native exception, or Hermes issue — stack trace, adb logcat/Xcode console, source maps | t1k-rn-base-debugger |
| Code review of RN code — perf pitfalls, bridge overhead, memory leaks, TypeScript correctness | t1k-rn-base-reviewer |
Performance profiling, bundle optimization, native-module perf work (Hermes profiler, FlashList, bundle-visualizer) — only when the performance module is installed | t1k-rn-performance-optimizer |
Generic/perf-adjacent optimization or errorRecovery performance when the performance module is NOT installed | t1k-rn-base-developer |
The optimizer role is conditional on module install
Section titled “The optimizer role is conditional on module install”optimizer does not have a single owner in this kit. Resolution depends on whether the
performance module is installed:
performancemodule installed → module overlay.claude/modules/performance/t1k-routing-performance.json(p92, additive to the kit’s p90) wins →optimizer=t1k-rn-performance-optimizer(same for file globs**/native/**,**/NativeModules/**and errorRecoveryperformance).performancemodule not installed → kit fragment.claude/t1k-routing-rn.jsonp90 →optimizer=t1k-rn-base-developer(which declaresroles: [implementer, optimizer]).
Read the module state — don’t infer optimizer from a single fragment.
Related
Section titled “Related”The tie-break rule (a task naming an RN domain concept takes its row above even when it also
touches shared code) and any unsummoned constraint live in .claude/modules/base/rules/agent-domain-routing-rn.md — read that first; it tells you when to consult this table.