This entry is a ready-to-use AI prompt — copy it and paste into ChatGPT, Claude, or Gemini.
Summary
The video teaches Commander deckbuilding through "engine" design: a repeatable system that converts one resource into another at scale, structured as enablers (inputs) and payoffs (outputs). The common mistake is filling a deck with on-theme cards without building a fluid engine. Good enablers are cheap in mana value, self-sufficient (work alone, no other card needed), and consistent/repeatable (upkeep triggers, activated abilities, common triggers); not every enabler hits all three, so accept trade-offs. Bad enablers are too expensive or need other cards to function (examples cited: Rox Faithmender, Sunscorch Regent, Wolverine Riders). Payoffs are the reverse—convert the resource into creatures, card draw, damage, or mana—but must actually close the game (Archangel of Thune, Vito, Angelic Accord), not just generate more value. Play fewer payoffs than enablers since payoffs are dead without enablers. Recommended counts: roughly 12 inputs and 6 outputs (within a 21-card theme section, leaving 3 slots for multiplier/synergy cards like Parallel Lives). The commander itself can be an input or output, shifting how many of each you need based on its cost and consistency (Thrasios as output, Aluren as input). Build by starting with payoffs and working backward, then goldfish the deck.
Key Clips
- [02:00] An engine is a repeatable system that converts one resource into another one at scale. Kind of like a factory.
- [03:34] You can play an Awakening Zone to create token creatures that are also mana, but then convert that resource of creatures into card draw with the classic Skullclamp. The process of conversion requires an input and an output, or more commonly known as the enabler versus the payoff.
- [03:34] You want your enablers to be cheap in mana value because if your entire engine is dependent on this resource, you don't want to wait till later in the game to get your engine going. You also want your enablers to be self-sufficient — they work by themselves because they are your workhorse cards. And the last attribute is that they are consistent — repeatable in how it generates the resource.
- [07:55] The most common issue I see are designers choosing enablers that aren't simple or consistent enough. A Rox Faithmender will rot in your hand if you don't have a way to trigger it. The inputs are your setup cards and the most important thing is they need to be cheap.
- [08:00] At the top end of the mana curve, we're generally saving those spots for our payoffs, and they need to be more powerful to help us close a game. You really don't want your enabler cards to also sit in those mana values. If your deck isn't working, take a look at what the enablers are and make sure they are in the lower end of the range, and you have enough.
- [09:00] Outputs should focus more on threats or game enders, like Archangel of Thune, Vito, Thorn of the Dusk Rose, or Angelic Accord. We should also be playing fewer payoffs than enablers as most payoffs are generally useless until there is an enabler to support it.
- [10:46] Using the cube theory model, I always start with at least eight inputs and eight outputs because that's easier to remember. But it really should be at least 12 inputs and six outputs.
- [15:00] When it comes to designing the engine, we should start with some of the payoffs we want to win with and work in reverse so we can pick the right backbone to support it. Start with the payoff and work backwards. 12 enablers, six payoffs. Do that first and then goldfish it.
Tags
Archetypes/Strategy: value-engine, tokens, aristocrats, tribal, midrange Format/Bracket: Core, Upgraded, Optimized Card Categories: ramp, draw, removal, finishers, win-cons, recursion, utility