SEO guide
Slay the Spire 2 Deck Builds
A deck-build hub for Slay the Spire 2 covering character builds, support density, combo reliability, and patch confidence.
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.
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.