SEO guide
Slay the Spire 2 Silent Build Guide
A Silent build guide for discard, draw, poison-style planning, tempo checks, and patch-sensitive support density.
Quick answer
Silent build pages should focus on draw consistency and whether the deck has enough early damage before it becomes an engine.

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.
- Do not take payoff before enough enablers exist.
- Fix early damage before scaling.
- Use discard and draw cards to reduce bad hands.
Silent builds are card-flow tests
Silent can make many small-card and draw-heavy plans look smooth, but the build is only reliable when it reduces bad hands. A pile of payoff cards is weaker than a deck that finds damage, block, and engine pieces on time.
- Prioritize early damage before slow poison, discard, or shiv payoff.
- Take draw and discard when they improve hand quality, not just because they cycle.
- Check whether the deck can block while spending energy on setup.
High-ceiling runs need a weakness section
Silent highlight footage is useful when it also exposes what could have gone wrong. If the deck wins through huge card flow, the guide should still record how it handled early damage, bad draws, and bosses that demand block before the engine is ready.

- Write the required enablers before describing the payoff.
- Mark which fights punished slow setup or low block.
- Use recovery-run clips to explain what to do after a bad start.
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.