Original Build Framing
This site is not a card dump. Each character summary is written to explain pace, scaling windows, and the kinds of turns a deck is trying to assemble so players can make better draft decisions.
Slay the Spire 2
Editorial Guide
This site is not a card dump. Each character summary is written to explain pace, scaling windows, and the kinds of turns a deck is trying to assemble so players can make better draft decisions.
Cards, relics, and community builds are separated into clear views so visitors can inspect one problem at a time instead of scanning a single overloaded catalog page.
The project keeps English and Korean guidance side by side and supports additional interface languages so non-English players can compare names, archetypes, and planning notes faster.
The goal is to help with playable decisions: what a starter relic implies, why a card package matters, and how a build moves from Act 1 stabilization into payoff turns.
Build Principles
Early picks should solve hallway fights and elite pressure first. A strong late-game synergy that loses tempo in the first two acts is usually not a real plan.
Starter relics often reveal the cleanest first draft direction. The site surfaces those identity cues so players can identify when a run is pushing aggression, setup, or recursion.
Good builds are not random piles of strong cards. They establish a turn pattern: setup, convert, defend, and close. The build view is meant to show those lines clearly.
Too many low-impact cards blur a deckโs payoff turns. Use the editor to keep only the pieces that support the plan you can actually execute during combat.
Trust & Scope
Slay the Spire 2 Build Lab is an unofficial reference project. It is not affiliated with or endorsed by the gameโs publisher or developers.
Character summaries, build framing, and explanatory copy are editorially written for this site. The purpose is to add context and planning value beyond raw item lists.
If card text, relic behavior, or terminology changes during development, the site should be updated. Visitors can report corrections through the contact page.