Deck tags, card roles, and oracle tags: how they fit

Zwipe has three related tagging concepts, and they're easy to mix up. Here's how they fit together: deck tags seed oracle tags, oracle tags sharpen suggestions, and card roles sum up what a card's oracle tags say.

Deck tags: the archetype you pick

Deck tags label your deck's game plan, Aggro, Tokens, Reanimator, and so on. Picking one auto-selects the oracle tags that define it, so one pick sets up the rest.

Oracle tags: the specific things your deck does

Oracle tags are granular and functional: spot-removal, ramp, sacrifice-outlet. Deck tags seed a starter set, but you can add or remove them directly to fine-tune. Selected oracle tags are what sharpen which cards Zwipe suggests.

Card roles: the summary

Card roles are different from the other two: you never assign them, they're computed from a card's oracle tags. Those tags roll up into a small set of coarse roles, Removal, Ramp, Card advantage, shown as chips when you expand a card's row or open its rules. Tap a role to see the oracle tags underneath it. You can still filter the stack by role.

How it flows

You configure
  Deck tags
     │ seed
     ▼
  Oracle tags  (refine freely)
     │ match
     ▼
Zwipe serves
  cards that fit your deck

The more you set up a deck, the better its suggestions.

The one-liner

Tell Zwipe what your deck does, and it suggests cards that fit. Deck tags and oracle tags are how you tell Zwipe; card roles are how Zwipe shows you what any given card brings to the table.