Quick Start

• Extract explicit module names from user prompt first.
• If module is found, route by exact module mapping before keyword heuristics.
• If module is not found, use aliases and layer context.

Workflow

• Parse prompt for module candidates (for example RenderCore, AIModule, AssetRegistry).
• Lookup module in ue5-module-routing-table-final.csv.
• If multiple hits, prioritize:
  1. exact module name match
  2. Build.cs path similarity
  3. alias overlap with prompt keywords
• Return routing payload:
  • primary_skill
  • secondary_skill
  • recommended_mcp_tools[]
  • route_confidence
  • route_reason
• Use secondary_skill when request spans multiple concerns in one module context.