Slay the Spire 2 Deck Builds

Quick answer

Deck-build pages should teach how builds form naturally from rewards instead of forcing a pre-decided archetype every run.

What to check first

Use this page as a practical search-intent answer first, then follow the related database links for deeper card, relic, character, boss, and patch context.

• Start with what the run offers.
• Add payoff only after enough enablers exist.
• Use relics to decide whether a build is realistic.

A deck is a set of jobs

A strong deck is not just a theme. It has jobs: early damage, block, scaling, card flow, and a way to finish bosses. A build page should show which cards perform each job and what the deck does when one piece is missing.

• Explain the job of each core card group.
• Show replacement options when the perfect card never appears.
• Use final deck screenshots only after explaining the decisions that built it.

Build names are less important than support density

A named build can help readers search, but it can also make them force the wrong plan. The deck-build page should explain how many enablers, payoffs, defensive cards, and draw tools a plan needs before it becomes a real build.

• Count enablers and payoffs before naming the build.
• Write fallback plans for runs that miss one key card or relic.
• Use character build pages for character-specific support-density rules.

Quick answer

A deck build is ready to commit when it has enough support density to survive bad hands and enough payoff to beat bosses. Until then, draft by jobs: damage, block, draw, scaling, and route safety. Exact build rankings are needs verification after major patches because support density can change quickly.

Common mistake

The common mistake is naming the build too early. If the player calls a deck a shiv build, orb build, block build, or companion build before it has enough support, the label can make them ignore the next fight. Let the deck prove the build through rewards, relics, and boss prep.

Evidence to collect next

The next deck-build evidence pass should capture the reward screen where the build begins, the fight where it almost fails, and the boss turn that proves the payoff is real. Those three clips separate a repeatable build from a highlight deck. Keep exact support thresholds and patch-specific build rankings marked needs verification until repeated runs show the same pattern.

Editorial note

This page is part of the first English-only content batch. It is written conservatively for Early Access and should be tightened whenever a major patch changes public information or run data.