Damage, defense & engine timing
Ironclad Builds
Decide when Strength, Exhaust, Block, or self-damage has become a real engine — and when the run still needs a more basic combat answer.
Build directions
Slay the Spire 2 Builds
Start with your character, identify the engine your current run is already supporting, then move into the specific build guide for the decisions that actually matter.
What this page helps you do
Find real build directions
See which Early Access mechanics already form real build paths, not just loose keyword clusters.
Compare support depth
See how many cards, relics, and potions currently support each build direction.
Enter deeper decision pages
Jump into build pages that explain core plans, strengths, weaknesses, and supporting resources.
Start here
Choose Your Character
These guides answer the broad build question first. They help identify which engine the run is actually ready to support before sending you into the narrower archetype guide.
5
Characters
18
Build Guides
Card access & overlapping engines
Silent Builds
Judge whether Shiv, discard/Sly, or Poison is actually solving the current run, including the hybrid engines that let one action handle several jobs.
Open Silent build guide Orb queue & cycling decisions
Defect Builds
Work out whether the run needs more Channeling, Orb capacity, Focus, Evoke control, or a separate Claw and 0-cost damage engine.
Build directions
Two competing damage clocks
Necrobinder Builds
Compare Osty pressure with Doom scaling, then decide whether the second engine actually covers a weakness or only adds more setup.
Open Necrobinder build guide Generation, conversion & scaling
Regent Builds
Balance Stars, Forge, and Sovereign Blade growth, then stop investing once damage is solved and another part of the run becomes the bottleneck.
Build directions
Build selection
Start With the Run, Then Follow the Engine
A build guide is most useful after the run gives you a reason to use it. I do not start by deciding “this will be Poison” or “this will be Strength.” I first solve the current fights, then follow the relationships that are already becoming repeatable.
01
Start with your character
The character guide answers the broad question first: which engines are actually becoming viable in this run?
02
Follow the engine that already has support
Move into the specific Strength, Shiv, Orb, Doom, Star, or other Owner Page once the run gives you a real reason to commit.
03
Diagnose the deck instead of forcing a label
If the deck is already underway, check what it still lacks — damage, defense, scaling, access, Energy, or matchup coverage — before adding more synergy.
Build & Engine Guides
Use these pages once your run has enough support for a specific engine to change how future rewards should be judged.
Secondary & Experimental Directions
Real relationships that can carry a run, but usually need narrower support or a more specific reason before I commit.
Already in a run?
Find What Your Current Deck Actually Needs Next
Once cards are already in the deck, archetype labels become less useful than the relationships between them. Check whether the run still needs frontload, defense, scaling, card access, Energy, or a specific engine payoff before taking another matching card.
Research the pieces
Check the Data Behind the Build
Build pages handle the decision. The database pages are there when you need exact effects, upgrades, or relationships before making it.
Engine pieces
Cards
Check exact card effects, upgrades, pools, keywords, Powers, and relationships before deciding whether a reward actually supports the build.
Explore →
Passive relationships
Relics
Relics can change whether an engine needs more support, already has enough output, or can survive the setup turns required to function.
Explore →
Fight-specific fixes
Potions
Use consumables to cover one dangerous elite or boss turn without permanently changing a deck whose core engine already works.
Explore →
Adjacent build questions
Slay the Spire 2 Build FAQ
Do I need to choose one build at the start of a Slay the Spire 2 run?
No. Early rewards usually need to solve immediate combat problems first. I start committing only after several cards, relics, or repeated actions point toward the same engine strongly enough that future rewards change value.
Can one deck use more than one build archetype?
Yes. Hybrid decks are often strongest when the same cards or actions support several roles at once. The problem is not mixing archetypes; it is running multiple packages that each need separate setup and compete for draw, Energy, or upgrade priority.
How do I know when a build is actually online?
I look for repeatability rather than a fixed number of synergy cards. The engine should happen often enough that I can reasonably expect it during important fights without requiring the perfect hand or several future rewards to rescue it.
Should I always take a card that matches my current build?
No. Once a role is already solved, another matching card can add less value than Block, draw, Energy, frontloaded damage, or a matchup-specific answer. A build label should never override what the current deck still needs.
When is skipping a card reward better than adding another build piece?
Skip becomes attractive when the offered cards mostly duplicate roles the deck already handles. Keeping the deck focused can improve access to the cards that already solve damage, defense, scaling, and important boss turns.
Should Beta balance changes change which build guide I use?
Usually start with the same build structure, then check whether a recently changed card affects the specific engine you are playing. Individual card values can move before the larger relationship between enablers, payoffs, and combat roles changes.
Keep exploring
Related Decision Hubs
Relics
Browse relic support and find what strengthens each build direction.
Potions
See which potions matter most for survival, burst, and scaling turns.
Synergies
Explore mechanics across cards, relics, and potions through shared tags.
Deck Evaluator
Input your deck and see what build direction your run is drifting toward.