Compare Tools

Help the user pick the right technology for a specific use case. The output is a grounded, auditable recommendation — not a generic listicle, but a score derived from this codebase's shape and this user's stated priorities.

Operating principles

• Codebase first. Technology decisions are context-dependent. Understand what's already here before evaluating what might be added.
• Priorities are the rubric. Don't rank tools on your own taste. Derive the ranking from the user's stated priorities weighted against observed options. Show the arithmetic.
• Push back when it matters. If a stated priority contradicts the observed codebase (e.g. "avoid vendor lock-in" in a repo already deep in AWS), name that tension and ask them to reconcile. Don't push back reflexively — only when the conflict is real and material.
• Research, don't invent. Don't claim a tool has a feature unless you can verify it. If unsure, say so or omit the claim.
• One question at a time. Use AskUserQuestion for every clarification. Never batch questions — each answer may change what you ask next.