Deck Comparison

Generate a prompt comparing two decks. Paste into ChatGPT, Claude, or Gemini.

Compare two Commander decks side by side, generate an AI-ready comparison packet, and paste the returned deck_comparison JSON back here for a readable verdict.

Follow the steps in order: enter both decks, generate the comparison packet, paste 30-comparison-prompt.txt into your AI, then paste the returned deck_comparison JSON into Step 3.

Save your work in progress to a zip file you can re-import later.

Resume from a saved session (.zip)

Choose a .zip file you previously downloaded from Step 3. This rehydrates the response JSON and jumps back to the comparison results step.

Saved session file

Step 1

Enter both decks

Each side accepts the same sources as the current Deck Analysis workflow: a public Moxfield or Archidekt URL, or pasted deck export text.

Required

Show Commander bracket definitions

Choose the bracket that best reflects each deck's intended power band. The comparison prompt includes these definitions so your AI judges the lists against the selected bracket expectations instead of guessing.

Bracket 1: Exhibition: Prioritize theme, unusual ideas, flexible legality, and showcase gameplay over optimization. Expect to play at least nine turns before you win or lose.
Bracket 2: Core: Unoptimized and straightforward decks with incremental, disruptable wins and low-pressure gameplay. Expect to play at least eight turns before you win or lose.
Bracket 3: Upgraded: Strong synergy, high card quality, meaningful interaction, and explosive but earned wins. Expect to play at least six turns before you win or lose.
Bracket 4: Optimized: Fast, lethal, efficient decks with strong game changers, fast mana, tutors, and explosive play. Expect to play at least four turns before you win or lose.
Bracket 5: cEDH: Metagame-tuned competitive Commander decks built for maximum efficiency and consistency. Games can end on any turn.

Moxfield URL support requires the DeckFlow Bridge extension → Install it here

DeckFlow's server cannot reach Moxfield reliably, so Moxfield URLs in this app go through the DeckFlow Bridge extension, which fetches the deck from your logged-in browser. Install it once, allow this site, and every future Moxfield URL import just works.

Download DeckFlow Bridge (.zip) Full install instructions →

Download the ZIP above and unzip it anywhere on your machine.
Load unpacked in Chrome/Edge: open chrome://extensions, enable Developer mode, click Load unpacked, and pick the unzipped deckflow-bridge folder.
Allow this site — open the DeckFlow Bridge Options page and add this DeckFlow origin to the allowed-origins list.
Retry — paste the Moxfield URL here again and submit. The DeckFlow Bridge intercepts automatically.

Can't install? Make the Moxfield deck public, or use Moxfield's Bulk Edit view and paste the deck export text into the text field instead.

Want your Moxfield tags and categories to come through? Use Bulk Edit →

Moxfield's Bulk Edit view lists every card with its #tags inline — copy it, paste it into the text field here, and the tags travel with the deck. No extension required.

Open your deck on moxfield.com.
Click Bulk Edit. The Main Deck tab opens by default, with each card formatted like 1 Card Name (set) cn #Tag #Other.
Copy the Main Deck contents and paste them into the text field here. Run Compare — tags are preserved end-to-end.

Deck A name (optional) Optional. If blank, the comparison will fall back to the parsed commander or a generic Deck A label. Deck A bracket Required. This sets the expected power band and pacing for Deck A. Deck A URL or deck text Required. Paste a public deck URL or raw deck export text.

Deck B name (optional) Optional. If blank, the comparison will fall back to the parsed commander or a generic Deck B label. Deck B bracket Required. This sets the expected power band and pacing for Deck B. Deck B URL or deck text Required. Paste a public deck URL or raw deck export text.

Step 2

Generate the comparison packet

Generate the packet, copy 30-comparison-prompt.txt, paste it into your AI, then ask for the final answer plus the fenced deck_comparison JSON block.

Packet output

Analyze with

ChatGPT Claude

What you do:

Click Generate Comparison Packet.
Copy 30-comparison-prompt.txt.
Paste it into your AI.
Have your AI return the readable comparison plus a fenced ```json block whose top-level object is deck_comparison.
Use 32-comparison-follow-up-prompt.txt later if you continue the conversation with your AI and want refreshed JSON.
Paste that JSON into Step 3.

Show extra prompt presets

Best-Practice Header

Prepend this to any comparison prompt when you want tighter evidence discipline.

Use the decklists as the primary evidence base.
Do not invent card text, archetype details, or matchup claims.
When a conclusion is directly supported by the list, treat it as evidence.
When a conclusion depends on pattern recognition or likely play patterns, label it as inference.
If the list is insufficient to support a confident claim, say so clearly.

Quick Verdict Prompt

Use this when you want a short comparison outside the full app workflow.

Compare these two Magic: The Gathering decks in [FORMAT] at [POWER LEVEL].

For each deck, identify:
- core game plan
- main win conditions
- biggest strengths
- biggest weaknesses

Then give:
- a short side-by-side comparison
- which deck is stronger overall
- why

Be explicit about what is direct evidence from the decklists versus inference.

Deck A ([DECK A NAME]):
[DECK A LIST]

Deck B ([DECK B NAME]):
[DECK B LIST]

All-In-One Prompt

Use this for a detailed human-readable comparison without strict JSON output.

Compare these two Magic: The Gathering decks in detail for [FORMAT] at [POWER LEVEL].

For each deck, explain:
- game plan
- commander or focal card role
- setup speed
- win conditions
- strengths
- weaknesses
- consistency
- resilience
- interaction
- closing power

Then compare:
- how the matchup plays out head-to-head
- what cards or packages create the biggest gap
- which deck is stronger in a vacuum
- which is better into a typical meta
- which is more explosive
- which is more resilient

Finish with:
- a readable side-by-side summary
- a final verdict
- 5 concrete card or package differences that best explain the result

Be explicit about direct evidence versus inference.

Deck A ([DECK A NAME]):
[DECK A LIST]

Deck B ([DECK B NAME]):
[DECK B LIST]

Strict JSON Prompt

Use this when you want output shaped for the app's deck_comparison JSON step.

Compare these two Magic: The Gathering decks in [FORMAT] at [POWER LEVEL].

Analyze:
- deck identity and overall game plan for each deck
- commander role and deck thesis
- speed and setup tempo
- ramp, draw, interaction, board wipes, recursion, and finishing power
- consistency and resilience
- strengths and weaknesses of each deck
- major overlap and major differences
- which deck is stronger in a vacuum
- which deck is more resilient
- which deck is more explosive
- which deck is likely better at a typical [FORMAT] table
- recommended audience or playgroup fit for each deck
- 5 concrete cards or packages that best explain the gap

Output requirements:
- start with a readable comparison summary
- then give a side-by-side comparison
- then give a final verdict
- then return a fenced ```json block
- inside that block, return a top-level object named "deck_comparison"
- the JSON must be valid and must match the schema exactly
- if evidence is limited, say so in confidence_notes

Schema:
{
  "deck_comparison": {
  "deck_a_name": "[DECK A NAME]",
  "deck_b_name": "[DECK B NAME]",
  "deck_a_commander": "",
  "deck_b_commander": "",
  "deck_a_gameplan": "",
  "deck_b_gameplan": "",
  "deck_a_bracket": "",
  "deck_b_bracket": "",
  "shared_themes": [],
  "major_differences": [],
  "deck_a_strengths": [],
    "deck_b_strengths": [],
    "deck_a_weaknesses": [],
    "deck_b_weaknesses": [],
    "speed_comparison": "",
  "resilience_comparison": "",
  "interaction_comparison": "",
  "mana_consistency_comparison": "",
  "closing_power_comparison": "",
  "combo_comparison": "",
  "overall_verdict": "",
  "key_gap_cards_or_packages": [],
  "deck_a_key_combos": [],
  "deck_b_key_combos": [],
  "recommended_for": {
    "deck_a": [],
    "deck_b": []
    },
    "confidence_notes": []
  }
}

Separate direct evidence from inference.

Deck A ([DECK A NAME]):
[DECK A LIST]

Deck B ([DECK B NAME]):
[DECK B LIST]

Step 3

Paste the returned comparison JSON

Paste only the fenced JSON block or raw JSON payload that contains the top-level deck_comparison object.

Final step

Deck comparison JSON Required for rendering the final summary. You can paste the fenced ```json block directly.