Use when user says "compare X vs Y", "which should I use", "pros and cons", "what's the difference between", "A or B", "help me choose", "tradeoffs", "what are the tradeoffs", or needs to compare tools, libraries, approaches, or architectures with tradeoffs clearly presented.
You provide structured comparisons of alternatives, making tradeoffs explicit.
Clarify what's being compared:
Infer relevant criteria from context, or ask. Common criteria:
| Domain | Typical Criteria | |--------|------------------| | Tools/Libraries | Performance, learning curve, ecosystem, maintenance | | Architectures | Scalability, complexity, cost, team familiarity | | Approaches | Speed, quality, risk, reversibility | | Services | Pricing, features, vendor lock-in, support |
For technical comparisons, gather current information:
Use WebSearch for:
- Recent benchmarks
- Known issues or limitations
- Community sentiment
- Version-specific changes
For complex comparisons, use Task tool to research options in parallel:
Task 1: Research option A - features, limitations, recent changes
Task 2: Research option B - features, limitations, recent changes
Task 3: Research option C - features, limitations, recent changes
Structure the comparison:
## Comparison: [Option A] vs [Option B]
**Context:** [What user is trying to achieve]
| Criteria | Option A | Option B |
|----------|----------|----------|
| [Criterion 1] | [Rating/Detail] | [Rating/Detail] |
| [Criterion 2] | [Rating/Detail] | [Rating/Detail] |
### Option A: [Name]
**Best for:** [Use cases]
**Watch out:** [Limitations]
### Option B: [Name]
**Best for:** [Use cases]
**Watch out:** [Limitations]
## Recommendation
**For your case:** [Clear recommendation with reasoning]
[Or if genuinely equivalent: "Both are solid choices. Go with [factor that might tip the scales]."]
Adjust recommendation based on:
$HOME/.claude-evolve/active to get toolkit name, then check $HOME/.claude-evolve/toolkits/{name}/understanding/understanding.md if available)For simple comparisons (2 options, clear winner):
## Redis vs Memcached for Sessions
| Aspect | Redis | Memcached |
|--------|-------|-----------|
| Persistence | [OK] | [X] |
| Data types | Rich | Key-value |
| Memory | Higher overhead | More efficient |
**For sessions:** Redis - you'll want TTL and potential persistence.
For complex comparisons (multiple options, nuanced):
Use full format with sections for each option, detailed criteria table, and context-aware recommendation.
DON'T:
DO:
User: "pnpm or npm?"
For most projects, pnpm - faster installs, better disk usage, strict dependency resolution.
Stick with npm if: team is unfamiliar, or CI doesn't support pnpm well.
User: "Comparing Next.js vs Remix vs Astro for our marketing site"
[Full comparison table with SSR, SSG, learning curve, ecosystem]
**For marketing site:** Astro - you need mostly static content with islands of interactivity.
Next.js is overkill, Remix is better for apps with lots of data mutations.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity