About

Why This Site Exists

Slay the Spire 2 Build Lab exists to turn raw card and relic data into a practical deckbuilding reference that helps players understand why a build works, not just what it contains.

Purpose

Readable Strategy Over Raw Lists

Many game reference pages stop at database presentation. This project is meant to go further by organizing characters, relics, and build choices around actual play decisions: early stabilization, scaling payoffs, and the turn patterns that define winning decks.

The main application lets visitors browse cards, inspect relic context, and create sample build lists. Those interactive tools are supported by editorial sections that explain how to use the information rather than treating data exposure as the final product.

What Is Original Here

Data Is Framed Around Decisions

The site uses game terms and item names because visitors need a reliable way to find the thing they saw during a run. The added value is the surrounding structure: character pressure points, role-based filters, build notes, timing advice, and bilingual explanations that help a player decide what to do next.

A raw card description answers what a card says. Build Lab tries to answer a different set of questions: when that card is worth taking, what problem it solves, what kind of deck can afford it, and which resource bottleneck it may create later.

Audience

Who The Project Is For

New Players

Players who know the genre but do not yet understand how each Slay the Spire 2 character converts weak early turns into stable runs.

Returning Players

Players checking updated card pools, renamed items, or build directions after balance changes and early access iteration.

Multi-Language Visitors

Players who want to compare English and Korean naming, recognize archetype vocabulary, and build decks without losing meaning across translations.

Editorial Responsibility

Corrections Are Part Of The Site

Slay the Spire 2 is still changing, so a useful reference has to be correctable. Visitors can report mismatched names, outdated effects, translation issues, or confusing strategy notes through the contact page. Reports are most useful when they include the character, card, relic, or potion name and the screen where the issue appeared.

The site avoids presenting community builds as universal answers. A build note should explain assumptions such as relic support, upgrade order, potion availability, and path pressure, because copying a card group without those conditions can mislead new players.

Standards

Editorial Principles

Original Explanation

Guides and summaries should add interpretation and practical context instead of duplicating publisher text without explanation.

Useful Navigation

Visitors should be able to move from overview to details quickly, with dedicated pages for policies, methodology, and contact information.

Clear Scope

The site focuses on deckbuilding and reference value. It should avoid misleading claims, scraped filler, or pages made only to host ads.