Tune a Commander deck without replacing its identity
Improve weak slots, mana and consistency while keeping the commander, archetype and play pattern that made the deck worth building.
Write the brief before changing cards
A tune should begin with the current deck, not with a generic list from the same color identity. Name the commander, target bracket, budget, preferred gameplan and any combo or tutor limits. If the archetype field is left empty in Esper Forge, Espi is instructed to infer and preserve the current plan instead of silently choosing a new one.
Also name the cards or experiences that are non-negotiable. A pet card, a lore restriction or a deliberately strange win condition can be more important than theoretical efficiency. Without that information, an optimizer may solve the wrong problem perfectly.
Repair foundations before luxury slots
Low land counts, missing colored sources, insufficient card draw and narrow interaction cause more losses than an imperfect finisher. Fix those categories first. Esper Forge protects a mana base of 40 or fewer lands from land-to-nonland swaps and asks a tune proposal to maintain or improve ramp, draw, interaction, protection, finishers and commander synergy.
One-for-one swaps make the proposal auditable. The incoming card is staged in the Sideboard and the outgoing card in the Maybeboard. Nothing becomes part of the main deck until the brewer applies the complete proposal or an individual swap.
Upgrade roles, not price tags
A replacement is better when it performs the same required job more reliably, fits the curve, supports the commander or removes a recurring weakness. A more expensive card is not automatically an upgrade. Store preference and currency should shape the budget calculation, while collection-aware tuning should be a deliberate choice because owned cards may already be allocated to another deck.
Bracket changes also need coherent swaps. Adding a Game Changer solely to raise a number can damage the gameplan. Espi is expected to prefer a verified card that supports the commander or repairs a real structural deficit, and to say when the requested power target cannot be reached without forcing a different style.
Apply, test and keep evidence
Apply a small group of related changes, play several representative games, then check whether the targeted weakness improved. A proposal can be legal and statistically cleaner while still feeling wrong in a particular pod. Use the deck-history view to compare additions and removals rather than relying on memory.
If the deck changes while a proposal is open, recalculate before applying it. That stale-state warning prevents an old recommendation from removing a card that no longer exists or breaking a deck size that has already changed. Tuning is safest when every recommendation is grounded in the current saved list.
Open your workspace or start with a private guest draft.
Checking…