TLDR
Start with 36 lands, 11 ramp cards, 10 card-advantage pieces, 11 forms of interaction, four protection cards, four recovery cards, 12 engine enablers, and 11 payoffs, plus your commander. Treat those numbers as a diagnostic baseline, not a law. Give every card one primary job, play five games, and adjust the categories associated with repeated failures before adding another exciting finisher.
A commander deck skeleton is the functional frame beneath the theme. It ensures your deck can develop mana, find cards, answer threats, protect its engine, recover from disruption, and eventually win. Artifact and Vehicle lists can compress several of those jobs into synergistic cards, but synergy does not excuse missing structural support.
Commander normally uses a commander plus 99 other cards, follows singleton construction outside basic lands, and restricts the deck according to the commander's color identity. The official Commander format overview provides the construction details. Within that legal frame, the skeleton below gives every one of the 100 slots an initial assignment.
A 100-card Commander deck skeleton
| Primary role | Starting slots | What the category must accomplish |
|---|---|---|
| Commander | 1 | Establish color identity and support the main plan |
| Lands | 36 | Make early land drops and provide the colors the deck needs |
| Ramp and mana production | 11 | Move the deck ahead of the normal one-land-per-turn curve |
| Card advantage and selection | 10 | Find resources and keep cards flowing beyond the opening hand |
| Targeted interaction | 8 | Answer individual permanents, spells, or graveyard plays |
| Board wipes | 3 | Reset opponents who develop faster or wider |
| Protection | 4 | Preserve a commander, engine, or decisive turn |
| Recovery | 4 | Rebuild after removal, discard, milling, or a wipe |
| Engine enablers | 12 | Create the conditions that make the deck's theme work |
| Payoffs and win conditions | 11 | Convert the engine into pressure, control, or a victory |
| Total | 100 | A complete first draft, not a universal optimum |
These categories resemble the functional approach used by public deckbuilding templates, which commonly separate lands, ramp, card flow, and interaction. That is useful context, but no template proves one ratio correct for every commander or playgroup. Your mana curve, commander, colors, engine speed, and expected opposition all matter.
The table is intentionally conservative. It gives a new list enough infrastructure to reveal what its theme can actually do. Once the deck functions, you can move slots between categories with evidence from games rather than optimism from the deck editor.
Assign every card one primary job
Commander cards love doing several things at once. An artifact creature might produce mana, crew a Vehicle, trigger an artifact payoff, and become an attacker later. That overlap is valuable, but counting the same card in four categories hides structural weaknesses.
During initial construction, count each card once according to the job you most need it to perform. If you expect a mana rock to accelerate you on turn two, classify it as ramp even if it can draw a card much later. If a token maker exists primarily to provide pilots, classify it as an enabler even though those tokens can attack.
Then evaluate secondary functions during play. Role compression should make a functioning deck more resilient; it should not make a nonfunctioning spreadsheet look balanced. A five-mana artifact that draws cards when it enters is not a substitute for early card selection. A seven-mana creature that destroys one permanent is not the interaction you need against a dangerous turn-three engine.
Build the mana base around actual breakpoints
Thirty-six lands is a sound opening number for a typical list, not an automatic final answer. Start higher when the commander costs five or more, the deck must naturally hit several land drops, or land cards are part of the engine. You can start lower when the curve is genuinely compact and the deck has abundant cheap selection, but do not cut lands merely because the list contains expensive mana rocks.
I treat cheap ramp and big-mana amplifiers as different tools. A two-mana rock helps move a four-mana commander forward. A six-mana mana doubler may produce an absurd next turn, but it does not help keep a two-land opening hand. Big-mana lists often want 12 to 14 ramp pieces, with most of them contributing before the deck is already operational. For a deeper breakdown, see how much ramp a big-mana Commander deck needs.
Track the mana value that matters most. If your deck becomes functional at four mana, ask how consistently it reaches four. If its crucial turn requires eight mana, record whether that happens through a stable progression or only when one fragile artifact survives. Building big mana without losing the early game is mainly a question of sequencing dependable setup before spectacular amplification.
Artifact synergy does not replace deck structure
Artifact decks are especially good at convincing brewers that every thematic card is infrastructure. It is an artifact, the commander mentions artifacts, and therefore it must belong. That logic produces gorgeous opening hands containing three payoffs, two recursion cards, and nothing productive to cast.
Ask what each artifact does before the engine is assembled. Mana rocks count as ramp when they increase usable mana on the relevant turns. Cheap artifacts that replace themselves can support card flow or enable artifact-count payoffs, but they are not automatically sustained card advantage. Cost reducers are enablers unless they reliably accelerate a large portion of the list.
Recursion deserves similar discipline. Scrap-based engines can generate excellent late-game value, but recovery does not replace development. Returning three artifacts from the graveyard is irrelevant if you missed land drops and never deployed them. Begin with enough mana and card flow to establish a board; add recursion to make that board harder to exhaust.
Your sweepers also need scrutiny. A general reset may destroy the mana rocks and utility artifacts keeping your deck alive. That can still be correct when an opponent is winning, but artifact-heavy lists should deliberately mix broad emergency buttons with asymmetric or selective answers where their colors permit.
Vehicle decks need a crew-capacity check
Vehicles create a second resource question: not just whether you can cast the cars, but whether you can drive them. Crew is an activated ability that taps creatures with enough combined power to meet the crew number, turning the Vehicle into an artifact creature until end of turn. The official Kaladesh release notes on crew explain the mechanic in detail.
There is no single mandatory Vehicle shell or color combination; community deck data includes Vehicle decks across multiple color identities. What matters is the balance between Vehicles and reliable crew sources in your specific list.
Count dependable pilots, not theoretical pilots. Cheap utility creatures, artifact creatures, repeatable token makers, and a commander that supplies bodies are excellent because they develop the board before your larger Vehicles arrive. A six-mana creature can technically crew a Vehicle, but it does nothing to prevent a three-mana Vehicle from sitting idle during the early game.
For every Vehicle, ask three questions:
- Can the deck cast this Vehicle on schedule without abandoning development?
- How many cards can crew it efficiently, and are those cards useful when the Vehicle is absent?
- Does the Vehicle create enough value when it attacks or triggers to justify needing another permanent?
If Vehicles are repeatedly stranded, the first fix is usually not another powerful Vehicle. Cut the weakest car for a low-cost creature, token engine, or artifact creature that performs another useful job. If pilots are stranded with nothing meaningful to crew, reduce narrow bodies or add Vehicles that matter without attacking immediately.
Diagnose two common failed builds
The showroom with no drivers
Imagine a list with 24 Vehicles, a commander, several Vehicle payoffs, and only a small group of creatures. Its best draws look impressive, but average draws spend mana deploying artifacts that cannot attack. The repair is structural: remove five or six of the least consequential Vehicles and add cheap pilots, token production, card selection, and flexible interaction. The deck becomes more thematic in actual games because its Vehicles finally operate.
The big-mana deck that starts on turn five
Now imagine an artifact deck packed with mana doublers, giant constructs, expensive draw engines, and recursion. It has plenty of power but too few plays before turn four. Cut several redundant top-end cards for lands, two-mana acceleration, and cheap card selection. You do not need six different ways to dominate after reaching ten mana; you need more ways to reach six mana without falling hopelessly behind.
Tune the skeleton through five focused games
Goldfishing helps with sequencing, but multiplayer games expose interaction, pressure, and recovery problems. Play five games before making sweeping changes unless a flaw is painfully obvious. If some uncertain cards are expensive or difficult to obtain, use clearly identifiable playtest cards or customizable MTG proxy printing to test the small package before committing to permanent copies. Keep test cards readable, sleeved consistently, and acceptable to your group; this guide to proxy cards for casual playtesting covers the practical setup.
After each game, record the same questions:
- Did the opening hand have a useful play by turn two or three?
- When did the deck reach its important mana breakpoint?
- Were Vehicles stranded without pilots, or were pilots stranded without useful Vehicles?
- Which cards stayed in hand because they were too slow, narrow, or expensive?
- Could the deck recover after its main board was removed?
- What action actually created a winning position?
- Which late draw felt embarrassingly weak, and what role should that slot serve instead?
Look for repetition. One missed third land can be variance; missing it in three games suggests the mana structure deserves attention. One Vehicle stranded after a wipe is normal; several opening hands full of uncrewed Vehicles indicate a construction problem. Change two to four cards, then run another set rather than rebuilding the entire deck after every loss.
Before testing, verify individual card legality against the current official Commander banned list, which the Official Commander Website says is updated quarterly. Card wording and legality can change, so check close to the game or publication date rather than relying on an old list.
Do not copy the skeleton directly into Commander Cube
A constructed commander deck controls its own proportions. A Commander Cube must let several drafters assemble functional decks from an uncertain pool, so a fixed 36-land or 11-ramp ratio does not transfer directly.
The underlying questions still transfer. Does the environment offer enough fixing and acceleration? Can drafters find card flow and interaction? Are artifact and Vehicle payoffs supported by enough broadly playable enablers? Are commanders flexible enough to survive imperfect drafts? In Cube design, think in terms of environment-wide density and draft access rather than a single 100-card checklist. Building an MTG Cube people want to draft again explores that broader balancing problem.
Fix the frame before adding another payoff
The best commander deck skeleton is not the one that preserves perfect category totals forever. It is the one that makes failures visible. Start with a complete functional frame, assign every card a primary role, and then let repeated games show where your commander bends the baseline.
When the deck stumbles, fix the earliest recurring failure first. Add mana before another eight-drop, pilots before another Vehicle, and card flow before another recursion loop. Once the deck consistently develops, interacts, and rebuilds, its unusual engines finally get the stage they deserve.