Updated March 7, 2026Written by Elias Rowe

About

About STS2 Wiki

STS2 Wiki publishes practical Slay the Spire 2 guides written to solve a player question in one read: what to pick, what to build first, and what mistakes to avoid. The site is built around one rule: every page should help a player make a better decision on the next run, not just restate game data in a different order.

STS2 Wiki content is written, edited, and reviewed by people who actively play Slay the Spire 2 before it is published on the site.

What we are building

Fast answers first, deeper strategy second.

Most STS2 pages should answer a player question before the second scroll. If the search intent is "Which class should I pick?" or "What does this relic actually change?", the page should solve that quickly and then offer deeper context underneath.

That is also why the site avoids thin filler, padded intros, and generic "pros and cons" blocks that could be pasted onto any game. If a section is not helping a real run decision, it should not be there.

Editorial principles

  • Write from a clear player point of view instead of source mashup language.
  • Only publish indexable pages when they answer a real search intent completely enough to be useful on their own.
  • Prefer practical advice, tradeoffs, and run-shaping decisions over filler or repeated definitions.
  • Keep revision dates visible and update pages when the game changes in a meaningful way.

What to expect

The site will stay opinionated.

The goal is not to sound neutral at all costs. Good wiki pages can still have a point of view. When a class is easier for new players, when a relic is bait, or when a build path is too inconsistent to recommend blindly, the page should say so clearly.

Editorial team

Who writes and reviews the guides

Marcus Vale

Lead Writer

Marcus is a veteran Slay the Spire player with more than 1,200 hours in the first game and a strong preference for practical, run-shaping advice over filler.

Elias Rowe

Editor and Site Builder

Elias builds and maintains the site, reviews strategy pages before they go live, and keeps the editorial side aligned with how the wiki is actually used.