Routing lab

Describe a project objective in natural language. The local browser matcher ranks repository semantic profiles, capabilities, domains, task categories, component descriptors, negative-match phrases, poor-fit scenarios, and the matrix baseline. This is an exploration aid, not a substitute for hard prerequisite checks.

How to use the result

1. Extract the project objective, constraints, environment, and desired outputs.
2. Match the request against semantic profiles, user-intent phrases, and task categories.
3. Apply do-not-select rules and prerequisite conditions before ranking candidates.
4. Evaluate relevant internal components rather than selecting only at repository level.
5. Compare setup effort, compatibility, maturity, security, and production readiness.
6. Apply repository relationships and combination rules when one repository is insufficient.
7. Return the selected repository IDs, component IDs, rationale, risks, and execution order.

Required output when an LLM makes the final selection

Ambiguity handling

• Do not select a repository based only on keyword overlap.
• Prefer verified capabilities over inferred capabilities.
• When two repositories are similarly suitable, compare differentiators and constraints.
• When confidence is low, state what additional project information is needed.
• Never invent undocumented components, paths, compatibility, or commands.