router-template
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese[Domain] Router
[业务领域] Router
Routes to N specialized skills based on task requirements.
根据任务需求将请求路由至N个专业技能。
Routing Protocol
路由协议
- Classify — Identify primary task type from user request
- Match — Find skill(s) with highest signal match
- Combine — Most production tasks need 2-4 skills together
- Load — Read matched SKILL.md files before implementation
- 分类 — 从用户请求中识别核心任务类型
- 匹配 — 找到信号匹配度最高的技能
- 组合 — 大多数生产环境任务需要同时搭配2-4个技能
- 加载 — 在执行前读取匹配到的SKILL.md文件
Quick Route
快速路由
Tier 1: Core (Always Consider)
第一层级：核心技能（优先考虑）
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | | word1, word2, word3 |
| 任务类型 | 技能 | 核心信号词 |
|---|---|---|
| [task] | | word1, word2, word3 |
Tier 2: Enhanced (Add When Needed)
第二层级：增强技能（按需添加）
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | | word1, word2, word3 |
| 任务类型 | 技能 | 核心信号词 |
|---|---|---|
| [task] | | word1, word2, word3 |
Tier 3: Reference Only
第三层级：仅作参考
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | | word1, word2, word3 |
| 任务类型 | 技能 | 核心信号词 |
|---|---|---|
| [task] | | word1, word2, word3 |
Signal Matching Rules
信号匹配规则
Priority Order
优先级顺序
When multiple signals present, resolve by priority:
- Explicit framework — React/Vue/vanilla overrides generic signals
- Specific feature — "multi-step wizard" beats generic "form"
- Platform constraint — mobile/VR/accessibility takes precedence
- Default tier — Fall back to Tier 1 core skills
当存在多个信号时，按以下优先级处理：
- 明确框架 — React/Vue/vanilla 优先级高于通用信号
- 特定功能 — "多步骤向导" 优先级高于通用 "表单"
- 平台约束 — 移动端/VR/无障碍需求优先
- 默认层级 — 降级至第一层级核心技能
Confidence Scoring
置信度评分
- High (3+ signals) — Route immediately
- Medium (1-2 signals) — Route with Tier 1 defaults
- Low (0 signals) — Ask user for clarification
- 高（3个及以上信号） — 直接路由
- 中（1-2个信号） — 结合第一层级默认技能路由
- 低（0个信号） — 请求用户澄清需求
Common Combinations
常见技能组合
[Scenario Name] (N skills)
[场景名称]（N个技能）
skill-1 → [what it provides]
skill-2 → [what it provides]
skill-3 → [what it provides]Wiring: [one-line integration summary]
skill-1 → [提供的能力]
skill-2 → [提供的能力]
skill-3 → [提供的能力]集成说明：[一句话集成概述]
[Scenario Name] (N skills)
[场景名称]（N个技能）
skill-1 → [what it provides]
skill-2 → [what it provides]Wiring: [one-line integration summary]
skill-1 → [提供的能力]
skill-2 → [提供的能力]集成说明：[一句话集成概述]
Decision Table
决策表
| Framework | Scale | Features | Route To |
|---|---|---|---|
| React | Standard | Auth form | skill-a + skill-b + skill-c |
| Vue | Standard | Data entry | skill-a + skill-d |
| None | Simple | Basic form | skill-e + skill-b |
| Any | Complex | Wizard | skill-f + skill-a + skill-b |
| 框架 | 规模 | 功能 | 路由目标 |
|---|---|---|---|
| React | 标准 | 认证表单 | skill-a + skill-b + skill-c |
| Vue | 标准 | 数据录入 | skill-a + skill-d |
| 无 | 简单 | 基础表单 | skill-e + skill-b |
| 任意 | 复杂 | 向导流程 | skill-f + skill-a + skill-b |
Fallback Behavior
降级处理逻辑
- Unknown framework → Use skill with broadest compatibility
- No clear signals → Ask: "What framework?" and "What's the core requirement?"
- Conflicting signals → Prefer Tier 1 skills, ask for clarification on Tier 2
- 未知框架 → 使用兼容性最广的技能
- 无明确信号 → 询问用户：“使用什么框架？”以及“核心需求是什么？”
- 信号冲突 → 优先选择第一层级技能，针对第二层级技能请求用户澄清
Reference
参考资料
See for:
references/integration-guide.md- Complete wiring patterns
- Code examples for all combinations
- Architecture diagrams
- Edge case handling
请查看 获取：
references/integration-guide.md- 完整的集成模式
- 所有组合的代码示例
- 架构图
- 边缘场景处理方案