Spire Builds exists for players who want concise, searchable strategy notes without digging through long videos or scattered comment threads. These standards keep the site useful, honest, and easy to correct as Early Access balance changes.
1. Advice Must Be Practical
Guides should explain what to do, why it works, and when it fails. If a strategy depends on a narrow relic, card reward, or patch-specific interaction, we say so instead of presenting it as universal advice.
2. Patch Dates Matter
Slay the Spire 2 is in Early Access. What works today might be nerfed next month. Guides include update dates, and pages that rely on patch-sensitive details are revised or clearly softened when we cannot verify them.
3. Facts, Analysis, and Testing Are Different
Official patch text and synchronized game data are cited as facts. Deck advice, rankings, and predictions are editorial analysis. A page is described as play-tested only when that work can be documented; patch-note analysis is never dressed up as personal run experience.
4. Corrections Are Public
When readers find errors, we fix them. For meaningful strategy changes, we update the page date and add clarifying language so readers can see that the advice changed.
5. No Content Scraping
We do not copy content from Steam forums, Reddit, Wiki pages, or other guide sites. If we reference community discoveries, we credit the source and add original decision context. Duplicate content helps no one.
6. Tools Do Not Replace Verification
Software can assist research organization, formatting, and quality checks. It cannot create a source, invent hands-on experience, or turn an early beta opinion into a settled fact. Unsupported claims are removed during editing, and source links remain visible to readers.
7. Affiliate and Ad Transparency
We run ads and may use affiliate links to support the site. This never influences what we recommend. If a build is bad, we say it is bad even if the cards are on sale somewhere. Affiliate relationships are disclosed where required by law.
8. Reader Feedback Shapes Content
We read every email and consider every correction. If enough readers say a guide is confusing or wrong, we rewrite it. The best way to reach us is shane768777@gmail.com.