smart-routing

Intelligent request routing for /toh command. Analyzes user intent, assesses confidence, detects IDE environment, and routes to the appropriate agent(s). Memory-first approach ensures context awareness. Triggers: /toh command, natural language requests, ambiguous inputs.

$ Instalar

git clone https://github.com/wasintoh/toh-framework /tmp/toh-framework && cp -r /tmp/toh-framework/src/skills/smart-routing ~/.claude/skills/toh-framework

// tip: Run this command in your terminal to install the skill


name: smart-routing description: > Intelligent request routing for /toh command. Analyzes user intent, assesses confidence, detects IDE environment, and routes to the appropriate agent(s). Memory-first approach ensures context awareness. Triggers: /toh command, natural language requests, ambiguous inputs.

Smart Routing Skill

Intelligent routing engine for the /toh smart command. Routes any natural language request to the right agent(s).


🧠 Routing Pipeline

┌─────────────────────────────────────────────────────────────────┐
│                    USER REQUEST                                 │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  STEP 0: MEMORY CHECK (ALWAYS FIRST!)                          │
│  ├── Read .toh/memory/active.md                                │
│  ├── Read .toh/memory/summary.md                               │
│  ├── Read .toh/memory/decisions.md                             │
│  └── Build context understanding                               │
│                                                                 │
│  STEP 1: INTENT CLASSIFICATION                                 │
│  ├── Pattern matching (keywords, phrases)                      │
│  ├── Context inference (from memory)                           │
│  └── Scope detection (simple/complex)                          │
│                                                                 │
│  STEP 2: CONFIDENCE SCORING                                    │
│  ├── HIGH (80%+) → Direct execution                            │
│  ├── MEDIUM (50-80%) → Plan Agent first                        │
│  └── LOW (<50%) → Ask for clarification                        │
│                                                                 │
│  STEP 3: IDE DETECTION                                         │
│  ├── Claude Code → Parallel execution enabled                  │
│  └── Other IDEs → Sequential execution only                    │
│                                                                 │
│  STEP 4: AGENT SELECTION & EXECUTION                           │
│  └── Route to appropriate agent(s)                             │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

📊 Intent Classification Matrix

Primary Patterns → Agent Mapping

Pattern CategoryKeywords (EN)Keywords (TH)Primary AgentConfidence
Create UIcreate, add, make, build + page/component/UIสร้าง, เพิ่ม, ทำ + หน้า/componentUI AgentHIGH
Add Logiclogic, state, function, hook, validationlogic, state, function, เพิ่ม logicDev AgentHIGH
Fix Bugbug, error, broken, fix, not workingbug, error, พัง, ไม่ทำงาน, แก้Fix AgentHIGH
Improve Designprettier, beautiful, design, polish, styleสวย, design, ปรับ designDesign AgentHIGH
Testingtest, check, verifytest, ทดสอบ, เช็คTest AgentHIGH
Connect Backendconnect, database, Supabase, API, backendเชื่อม, database, SupabaseConnect AgentHIGH
Deploydeploy, ship, production, publishdeploy, ship, ขึ้น productionShip AgentHIGH
LINE PlatformLINE, LIFF, Mini AppLINE, LIFFLINE AgentHIGH
Mobile Platformmobile, iOS, Android, Expo, React Nativemobile, มือถือMobile AgentHIGH
New Projectnew project, start, build app, create systemproject ใหม่, สร้าง appVibe AgentHIGH
Planningplan, analyze, PRD, architectureวางแผน, วิเคราะห์Plan AgentHIGH
AI/Promptprompt, AI, chatbot, system promptprompt, AI, chatbotDev Agent + prompt-optimizerHIGH
Continuecontinue, resume, go onทำต่อ, ต่อMemory → Last AgentMEDIUM
Complex RequestMultiple features, system, e-commerce, etc.ระบบ + หลาย featuresPlan AgentMEDIUM
Vague Requesthelp, fix it, make better (without context)ช่วยด้วย, แก้ทีAsk ClarificationLOW

🎯 Confidence Scoring Algorithm

interface ConfidenceFactors {
  keywordMatch: number;      // 0-40 points
  contextClarity: number;    // 0-30 points
  memorySupport: number;     // 0-20 points
  scopeDefinition: number;   // 0-10 points
}

function calculateConfidence(request: string, memory: Memory): number {
  let score = 0;
  
  // Keyword matching (0-40 points)
  // Strong match with primary patterns = 40
  // Partial match = 20
  // No match = 0
  score += keywordMatchScore(request);
  
  // Context clarity (0-30 points)
  // Specific page/component mentioned = 30
  // General area mentioned = 15
  // No specifics = 0
  score += contextClarityScore(request);
  
  // Memory support (0-20 points)
  // Request relates to active task = 20
  // Request relates to project = 10
  // No memory context = 0
  score += memorySupportScore(request, memory);
  
  // Scope definition (0-10 points)
  // Single clear task = 10
  // Multiple related tasks = 5
  // Unclear scope = 0
  score += scopeDefinitionScore(request);
  
  return score; // 0-100
}

// Thresholds
const HIGH_CONFIDENCE = 80;    // Execute directly
const MEDIUM_CONFIDENCE = 50;  // Route to Plan Agent
// Below 50 = Ask for clarification

🖥️ IDE Detection

Detection Method

function detectIDE(): 'claude-code' | 'cursor' | 'gemini' | 'codex' | 'unknown' {
  // Check for IDE-specific markers
  
  // Claude Code detection
  if (hasClaudeCodeMarkers()) {
    return 'claude-code';
  }
  
  // Cursor detection
  if (hasCursorRules()) {
    return 'cursor';
  }
  
  // Gemini CLI detection
  if (hasGeminiConfig()) {
    return 'gemini';
  }
  
  // Codex CLI detection
  if (hasCodexConfig()) {
    return 'codex';
  }
  
  return 'unknown';
}

Execution Strategy by IDE

IDEMulti-Agent StrategyReason
Claude CodeParallel (spawn sub-agents)Native support for parallel tool calls
CursorSequentialMore predictable, follows diff flow
Gemini CLISequentialSafer execution model
Codex CLISequentialLinear task processing
UnknownSequential (default)Safe fallback

🔄 Routing Decision Tree

Request arrives
      │
      ▼
┌─────────────────────────────────────┐
│ 1. Load Memory Context              │
└─────────────────────────────────────┘
      │
      ▼
┌─────────────────────────────────────┐
│ 2. Is request "continue"/"ทำต่อ"?   │
├── YES → Read memory, resume task   │
└── NO → Continue analysis           │
      │
      ▼
┌─────────────────────────────────────┐
│ 3. Calculate Confidence Score       │
└─────────────────────────────────────┘
      │
      ├── Score >= 80 (HIGH)
      │   └─→ Select agent based on intent
      │       └─→ Execute directly
      │
      ├── Score 50-79 (MEDIUM)
      │   └─→ Route to Plan Agent
      │       └─→ Plan Agent analyzes & routes
      │
      └── Score < 50 (LOW)
          └─→ Ask clarifying question
              └─→ Wait for user response

📋 Clarification Patterns

When to Ask

SituationExampleAction
No verb/action"the login"Ask: "What would you like to do with login?"
No target"make it work"Ask: "Which page/component should I fix?"
Multiple interpretations"improve it"Ask: "Design, performance, or features?"
Missing context + no memory"fix it"Ask: "What's broken? Describe the issue."

When NOT to Ask

SituationExampleAction
Clear intent"create login page"Execute directly
Memory provides context"continue" + active task existsResume from memory
Reasonable default exists"add a button"Add to current page context

🎨 Skill Loading by Intent

Detected IntentSkills to Load
New Projectvibe-orchestrator, design-mastery, business-context, response-format
Create UIui-first-builder, design-excellence, response-format
Add Logicdev-engineer, error-handling, response-format
Fix Bugdebug-protocol, error-handling, response-format
Connect Backendbackend-engineer, integrations, response-format
Improve Designdesign-excellence, design-mastery, response-format
AI/Chatbotprompt-optimizer, dev-engineer, response-format
Testingtest-engineer, error-handling, response-format
Planningplan-orchestrator, business-context, response-format

Note: response-format skill is ALWAYS loaded for proper output formatting.


💾 Memory Integration

Pre-Routing Memory Check

Before routing, ALWAYS:
1. Read .toh/memory/active.md
   - Current task context
   - In-progress work
   - Blockers
   
2. Read .toh/memory/summary.md
   - Project overview
   - Completed features
   - Tech stack used
   
3. Read .toh/memory/decisions.md
   - Past architectural decisions
   - Design choices
   - Naming conventions

Use memory to:
- Boost confidence (if request matches active work)
- Provide context (for ambiguous "it" references)
- Maintain consistency (follow established patterns)

Post-Execution Memory Save

After routing completes, ALWAYS:
1. Update .toh/memory/active.md
   - Mark completed items
   - Update current focus
   - Set next steps
   
2. Add to .toh/memory/decisions.md
   - If new decisions were made
   
3. Update .toh/memory/summary.md
   - If feature was completed

⚠️ NEVER finish without saving memory!

📌 Examples

Example 1: High Confidence → Direct

Request: "/toh สร้างหน้า dashboard"

Analysis:
- Keyword match: "สร้าง" + "หน้า" = Create UI (40 pts)
- Context clarity: "dashboard" = specific page (30 pts)
- Memory: Project has other pages (15 pts)
- Scope: Single page (10 pts)
Total: 95 pts = HIGH

Route: UI Agent (direct)

Example 2: Medium Confidence → Plan First

Request: "/toh build e-commerce"

Analysis:
- Keyword match: "build" = Create (40 pts)
- Context clarity: "e-commerce" = general concept (10 pts)
- Memory: New project (0 pts)
- Scope: Multiple features (0 pts)
Total: 50 pts = MEDIUM

Route: Plan Agent first → then execute plan

Example 3: Low Confidence → Ask

Request: "/toh fix it"

Analysis:
- Keyword match: "fix" (20 pts)
- Context clarity: "it" = unclear (0 pts)
- Memory: No recent bugs (0 pts)
- Scope: Unknown (0 pts)
Total: 20 pts = LOW

Action: Ask "What would you like me to fix? Please describe the issue."

⚠️ Critical Rules

  1. Memory ALWAYS first - Never route without checking context
  2. Confidence drives action - Trust the scoring system
  3. Plan Agent is your friend - When in doubt, route to Plan
  4. IDE awareness matters - Parallel only in Claude Code
  5. response-format always loaded - Every response needs 3 sections

Smart Routing Skill v1.0.0 - Intelligent Request Routing Engine