Mechanics hub
Mechanic pages turn class identity into evergreen strategy coverage
The mechanics hub exists to bridge the gap between broad class pages and deeper builds. The first wave stays conservative: strength scaling, card sequencing, and orb management.
Cluster
Mechanics
Live pages
3
Status
Editorial reference
Expansion path
Cards + relics starting
Why the mechanics hub should exist now
Launch-week content usually starts with answers, classes, and safe starter builds. The next durable layer is mechanics.
Mechanic pages help the site explain ideas that sit underneath multiple routes:
- a class page can point to the mechanic it is best known for
- a build guide can point to the mechanic that explains its logic
- the hub can keep growing later into cards, relics, and deeper archetype pages
What the first three mechanic pages are trying to do
The first mechanic set should stay simple and reusable:
strength scalinggives Ironclad coverage a clean evergreen concept pagecard sequencingexplains why some Silent turns are about order, not only raw valueorb managementturns Defect's technical identity into a long-term reference route
These are good launch-wave mechanic pages because each one can connect to both a class page and a build page without pretending the entire meta is solved.
Why these pages should stay editorial
Mechanic pages are not official documentation. They are editorial reference pages.
That means they should do two things well:
- explain the concept in plain language
- stay honest about current confidence and not overclaim hidden certainty
How this cluster should scale later
Once the workflow is stable, the mechanics hub can grow outward into:
- deeper class-specific mechanic pages
- the cards hub and relic entity pages
- patch refreshes when a mechanic meaningfully changes
First mechanic pages
The first three reusable strategy references
Each one sits between a class page and a build page, so the cluster can expand cleanly later.
entity
Slay the Spire 2 Strength Scaling
Learn how to think about strength scaling in Slay the Spire 2 without pretending the launch-week meta is already solved.
entity
Slay the Spire 2 Card Sequencing
Learn how to think about card sequencing in Slay the Spire 2 and why order matters more than raw card value in some runs.
entity
Slay the Spire 2 Orb Management
Learn how to frame orb management in Slay the Spire 2 and why it makes Defect coverage more durable than a launch-week build list alone.
Next clicks
The two best parent clusters to connect after mechanics
Mechanic pages work best when they route users back into the class and build clusters that use the idea.
FAQ
Why this cluster matters early
Mechanic pages help the site scale past launch-week answers without jumping straight into fragile card-level depth.
Why launch a mechanics hub before cards and relics?
Because mechanic pages are the cleanest evergreen bridge between broad class identity and deeper per-run strategy coverage.
Are these mechanic pages official documentation?
No. They are editorial reference pages that stay anchored to confirmed roster context and cautious launch-week analysis.
Which mechanic pages are live first?
The first public set focuses on strength scaling, card sequencing, and orb management.