Slash Command

/compare

Structured comparison of two or more technologies. Same problem, different solutions — trade-offs made explicit.

npx claudepluginhub irfanabduhu/rune --plugin codemonk

Details

Argument[tech A] vs [tech B] [optional: for specific use case]

Prompt Preview

Structured technical comparison: $ARGUMENTS

1. **Frame the decision** — what problem does this choice solve? What are the actual selection criteria that matter (not marketing bullet points)? If a use case is specified, anchor everything to it.
2. **Mental models** — for each technology, explain its core philosophy in 2-3 sentences. What does it optimize for? What does it deliberately sacrifice? These philosophies predict behavior in edge cases.
3. **Head-to-head** — compare on dimensions that actually differ. Skip features both handle equally well. For each dimension: show concrete code/co...

Command Content

Other plugins with /compare

/compare

32.9k

Compares two skills head-to-head across quality dimensions, reporting which is better in each category. Accepts two arguments: <skill-a> and <skill-b>.

plugin-eval

/compare

1.0k

Compares current screenshots against baselines to detect visual regressions via pixel diff with threshold, generates diff images, summary table with pass/fail status, and report.

visual-regression

/compare

1.0k

Compares multiple ML experiment runs side-by-side from tracking store, analyzes parameter sensitivity, generates visualizations, identifies best configuration, and recommends next experiments.

experiment-tracker

/compare

328

Compares two or more stocks side by side using key metrics, valuation, growth, profitability, and recent performance data. Outputs a comparison table and analysis summary.

investor

/compare

Compares two container images <image1> <image2> to identify differences in metadata, layers, sizes, configuration, platform, and security.

container-image

/compare

Diffs two ComfyUI workflows from files, names, history, or IDs to show added/removed nodes and changed inputs/connections.

comfy

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitApr 11, 2026

Actions

View Source View Plugin View on GitHub View README

Structured technical comparison: $ARGUMENTS 1. **Frame the decision** — what problem does this choice solve? What are the actual selection criteria that matter (not marketing bullet points)? If a use case is specified, anchor everything to it. 2. **Mental models** — for each technology, explain its core philosophy in 2-3 sentences. What does it optimize for? What does it deliberately sacrifice? These philosophies predict behavior in edge cases. 3. **Head-to-head** — compare on dimensions that actually differ. Skip features both handle equally well. For each dimension: show concrete code/co...

Structured technical comparison: $ARGUMENTS

Frame the decision — what problem does this choice solve? What are the actual selection criteria that matter (not marketing bullet points)? If a use case is specified, anchor everything to it.
Mental models — for each technology, explain its core philosophy in 2-3 sentences. What does it optimize for? What does it deliberately sacrifice? These philosophies predict behavior in edge cases.
Head-to-head — compare on dimensions that actually differ. Skip features both handle equally well. For each dimension: show concrete code/config examples side-by-side, explain the trade-off, state who wins and why.
The uncomfortable truths — what does each technology's community downplay? Where does each one break down? What are the migration/lock-in costs?
Decision framework — don't say "it depends." Give concrete criteria: "Choose A when [specific conditions]. Choose B when [specific conditions]. Choose neither when [conditions]."

Output as [techA]-vs-[techB].md. Include runnable code examples for the same task in each technology. No false balance — if one is clearly better for the stated use case, say so.