Combos

What this surface is

Combos is the discovery surface for known combo lines and card pairs. It’s powered by Pegasus’s combo-intel ingest pipeline that extracts two-card combo pairs from community-contributed combo notes and tags them with a deterministic generated name. Use Combos to look up what a specific card pair does, browse combos by archetype, or discover combos your deck enables that you weren’t using.

Where to find it in the app

Navigate to /combos from the main nav. Combos also surface contextually:

• In Quick Analysis findings panel — when Pegasus detects a combo line in your deck
• In Compare takeaways — when a swap adds or removes a combo line
• In card detail panels — “Combos this card enables” section

Screenshot pending /img/docs/reference/combos-overview.png

The combos browse view. Each card shows the pair + generated name + tags.

Layout

Region	Purpose
Top toolbar	Search, archetype filter, source filter
Combo grid	One card per combo pair
Combo detail	Selected combo’s full breakdown — steps, requirements, end-board
Source attribution	Original combo note source (community contributor)

Combo entry fields

Field	Type	What it shows	Notes
Card A	card chip	First card in the pair
Card B	card chip	Second card in the pair
Generated name	text	Deterministic name from cards + archetype	Always shown — never the raw combo_name
Archetype	tag	Inferred archetype
Steps	ordered list	Per-step description from source
End-board	text + chips	What the combo establishes
Source	link	Original community note
Tags	chip list	Format, role, difficulty

Caution

Display rule: all combo surfaces show the generated name only. Raw combo_name from sources is often junk ("344", "1+2", non-Latin transcriptions, machine-translated nonsense) and never surfaces in user-facing UI. Pegasus generates a stable name from card identifiers + archetype.

Pair extraction model

Combo-intel ingests community combo notes and extracts two-card pairs that, when held together, enable a meaningful play sequence.

Stage	What happens
1. Ingest	Raw combo note pulled from the source feed
2. Parse	Step-by-step text and end-board parsed into structured form
3. Card resolution	Card names matched to the catalog (printing-agnostic)
4. Pair extraction	Two-card pairs identified — each pair is independently meaningful
5. List-combo filter	Tagged list combos are skipped to avoid false-positive duplicates
6. Generated name	Deterministic name from the cards + inferred archetype
7. Persist	Combo + pairs stored, surfaced in /combos and analysis findings

The list-combo dedup at step 5 was added in P4.5 — before that, tagged list combos generated duplicate pair entries that polluted combo-intel.

How combos appear in analysis

In Quick Analysis findings, each detected combo line shows:

• Pair: Card A + Card B
• Generated name
• Step sequence (collapsed by default)
• End-board summary
• Confidence (whether the pair is fully present or partial)

Interactions

• Click a combo tile → opens detail with full step sequence
• Click a card chip inside a combo → opens card detail
• Filter by archetype → narrows the grid to one archetype’s combos
• Search → matches against card names, generated name, and end-board text
• “Show in my decks” toggle → filter to combos enabled by ≥1 active deck

States and badges

Badge	Meaning
”In your decks”	At least one active deck enables this combo
”Partial”	You own one card of the pair but not the other
”Owned”	You own both cards
”List combo” filter	Excluded by default — these are deck-list snapshots, not card pairs
Source confidence chip	Confidence in the parse + attribution

Edge cases

Caution

• Combo shows the wrong end-board. The parse failed on a non-standard step description. Use the source link to verify against the original note; report via Troubleshooting if persistent.
• Two listed cards but no clear sequence. Some “pairs” extracted from very short combo notes lack a meaningful sequence. Treat them as discovery hints, not gospel.
• Generated name reads weird. The generator uses card identifiers + archetype — for cross-archetype combos the name may be unintuitive.
• Combo missing from your analyzed deck even though you own both cards. Confirm both cards are in main+extra (Pegasus analyzes the joined main+extra set, but two cards in side don’t count).

Related workflows

Build decks Combos discovered here become starting points for new target decks.

Analyze decks and scores The findings panel surfaces combos detected in your deck.

Related references

• Quick Analysis — where combos appear as findings
• Data sources and affiliation — where combo-intel sources from