Slay the Spire 2 Defect Guide

Best Defect Builds in Slay the Spire 2

Defect is the character where I care least about keeping a build visually pure. Lightning, Frost, and Dark can share the same Orb queue, while a Claw engine can still use Orbs for defense. What matters is whether the queue, card draw, and damage plan are solving different parts of the fight without fighting each other for setup time.

Orb Engine · Claw / 0-Cost 3 starting Orb Slots Dataset v0.107.1
Quick answer

Build the Orb engine in the order: Channel → fill → control → scale.

I do not take extra Orb Slots before I can fill the slots I already have, and I do not treat Focus as a substitute for Orb generation. Once the queue is full, every new Channel also becomes an Evoke decision. That is the point where Defect stops being a list of good Orb cards and becomes a real engine. If the run instead gives me repeated cheap attacks and enough cycling, Claw can become the primary damage route while Orbs remain support.

Starting state

Defect Starts With an Orb Engine — Not a Finished Orb Build

Defect starts with three Orb Slots, Cracked Core, Zap, and Dualcast. That gives the run passive Lightning and an immediate way to Channel and Evoke, so Orb mechanics begin mattering before the first reward screen.

I still do not read that starting package as “build Lightning.” Its first job is simply to supply free damage while I learn what the run needs. The first several rewards still have to survive ordinary fights.

Starting cards that matter
Zap Dualcast
Run progression

How a Defect Build Actually Forms

Opening floors

The starting Lightning Orb is damage, not a build commitment

Cracked Core gives me passive Lightning immediately, while Zap and Dualcast already teach the basic Defect rhythm: Channel something, let the queue work, then decide whether an Evoke is worth consuming the front Orb. That starting package makes Orb cards easy to use, but it does not mean every run should become a Lightning build.

I still take practical frontloaded damage and defense when those are the reasons early fights are costing HP. The starting relic is infrastructure, not permission to force one archetype.
Late Act 1

I start separating Orb generation from Orb scaling

The first important question is whether I can Channel often enough. Ball Lightning, Coolheaded, Chill, Darkness, and similar cards can build throughput. Only after that do extra Orb Slots and Focus start multiplying something that already works.

If the queue is often empty, I want channels. If every slot is already full and useful Orbs are being pushed out, I start valuing capacity and control differently.
Mid run

The order of the Orb queue becomes part of the build

Once all slots are occupied, Channeling another Orb is not just generation — it also changes which Orb Evokes. At that point I stop evaluating a card only by what it Channels. I also ask what will be pushed out, whether that Evoke helps this turn, and which Orb I need to preserve for later.

A mature Defect deck manages two resources at once: the cards in hand and the future value stored in the Orb queue.
Late run

I identify whether the deck lacks survival, burst, or timing

A late Orb deck may already generate plenty of passive value but still fail one specific job. Frost can stabilize defense, Dark can store damage for a later window, and Lightning can keep producing damage without another attack card. The missing piece matters more than making the dominant Orb type even more dominant.

I stop asking “which Orb build am I?” and start asking which Orb belongs in each slot for the next difficult fight.
The Defect-specific decision

Orb Slots Change Meaning as the Queue Fills

This is the part I check before calling an Orb card “good.” Empty slots, full slots, and a valuable front Orb create completely different reward and play decisions.

01

Empty slots: Channeling is the priority

An empty Orb Slot produces nothing. Early in a fight, I usually care more about getting useful Orbs online than about theoretical scaling that will only matter after the queue is established.

Can this deck reliably put useful Orbs into all of its available slots?

02

Full slots: every Channel is also an Evoke decision

Once the queue is full, a new Orb pushes the front Orb out. That means the same card can be defensive, offensive, or actively mistimed depending on which Orb is currently first.

What am I Evoking if I Channel this card right now?

03

More Orb Slots are only good if I can use them

Capacity increases the amount of passive value the deck can store, but it also delays automatic Evokes. If I add slots faster than I add Channeling, I can create several empty spaces and make the deck slower instead of stronger.

Will another Orb Slot create more active value, or only more unused capacity?

04

Focus multiplies a working queue

Focus is much more impressive when several Orbs are already triggering every turn. I treat it as multiplication rather than infrastructure: first establish useful Orb activity, then improve the output of that activity.

How many meaningful Orb triggers will actually benefit from this Focus?

05

Evoking now can be worse than waiting

The front Orb contains future value. A Frost Evoke may be worth saving for a large enemy turn, while a Dark Orb may need more time before its stored damage is the reason the fight ends. Queue control is often about refusing the first available Evoke.

Does the Evoke solve this turn, or am I spending future value too early?

Build directions

The Two Defect Build Families I Actually Separate

Lightning, Frost, and Dark are usually roles inside the same Orb system. Claw is different because its damage comes primarily from repeated card cycling, so I treat it as the clearest separate build family.

Passive output + queue control

Orb Engine Defect Build

Most Defect runs do not need to become a pure Lightning, Frost, or Dark deck. I care about whether the Orb queue produces the damage, defense, and timing the current fight needs.

Open Orb Engine guide →
Signals that tell me it is real
  • • The deck can Channel Orbs often enough to keep the Orb slots productive.
  • • Focus or other Orb scaling already improves several cards and passive effects at once.
  • • Frost, Lightning, or Dark Orbs are solving real combat roles instead of appearing only because an Orb card was offered.
What changes after I commit
  • • Additional Orb channels gain value because they can trigger Evokes instead of merely filling empty slots.
  • • Orb Slots become more attractive once I can actually fill and cycle them.
  • • Focus becomes stronger when several active Orbs benefit from it every turn.
How this build fails

The usual mistake is collecting scaling before the Orb engine has enough throughput. Extra Orb Slots with nothing to Channel into them, or Focus in a deck that barely uses Orbs, can spend rewards without fixing the current fight.

When I stop pushing it

If physical attacks or a Claw package already solve damage and the Orb side exists only as light defense or utility, I stop trying to turn every reward into Orb scaling.

Cards that define or connect this route
Ball Lightning Coolheaded Chill Capacitor Defragment Synchronize Darkness Biased Cognition
Cheap cards + repeated cycling

Claw / 0-Cost Defect Build

Claw becomes a real direction when the deck can repeatedly reach and replay cheap attacks without giving up the defense, draw, or Energy needed to survive while the damage grows.

Open Claw / 0-Cost guide →
Signals that tell me it is real
  • • Multiple useful 0-Energy cards already exist instead of one isolated Claw.
  • • Draw and cycling let the deck reach those cheap cards repeatedly.
  • • The deck has enough defense or Orb support that spending card slots on repeated attacks does not make dangerous turns collapse.
What changes after I commit
  • • Card draw becomes especially important because cheap cards only matter when they return to the hand quickly.
  • • 0-Energy support gains value after the density already exists.
  • • Frost or other defensive Orb support can remain valuable even when attacks become the main damage engine.
How this build fails

One Claw does not justify filling the deck with mediocre 0-cost cards. A Claw deck that cannot cycle quickly enough is simply a collection of small attacks waiting several turns to become relevant.

When I stop pushing it

If I am not repeatedly drawing the cheap cards, or the deck needs scaling that does not depend on repeated attack cycles, I keep Claw as incidental damage instead of forcing the whole run around it.

Cards that define or connect this route
Claw All for One Scrape Beam Cell FTL
Inside an Orb build

Lightning, Frost, and Dark Solve Different Jobs

I usually do not need to choose one Orb type and reject the others. What matters is whether each Orb earns its position in the queue.

Passive and repeated damage

Lightning

Lightning is useful when I want damage to keep happening without spending every future card play on attacks. Early Lightning can help stabilize ordinary fights, but I do not keep drafting Lightning cards simply because the first few were good.

I want it when

I want steady damage while the hand spends Energy setting up, defending, or cycling.

I stop adding it when

Damage is already sufficient and another Lightning card does not improve AoE, scaling, or a specific matchup.

Zap Ball Lightning Thunder
Passive defense and burst Block

Frost

Frost changes the deck by moving part of defense out of the hand and into the Orb queue. That can make draw order much safer, but the queue still needs enough Frost density and scaling to cover the enemy turns that actually matter.

I want it when

My damage engine is developing but ordinary bad defensive draws are still costing too much HP.

I stop adding it when

Passive defense already covers normal turns and the deck instead lacks damage, scaling, or a way to finish Bosses.

Coolheaded Chill Cold Snap
Stored damage and timed burst

Dark

Dark Orbs reward patience. Instead of asking whether the Orb deals enough damage immediately, I ask whether the fight gives it time to grow and whether I can preserve or Evoke it on the turn where that stored damage matters.

I want it when

The deck can survive but needs a reliable way to convert several setup turns into one large damage window.

I stop adding it when

The fight demands immediate frontload or the queue cannot preserve the Dark Orb long enough for the stored damage to justify the slot.

Darkness Consuming Shadow
Why Orb control matters in real fights

Boss Mechanics Can Change Which Orb I Preserve

Defect has matchups where an Orb solves the mechanic for a reason that has little to do with a generic card tier. These are the situations I use to decide what stays in the queue.

Vantom

Passive Lightning can solve a mechanic before I change the whole deck

Vantom starts with Slippery, so repeated instances of damage matter. Defect already enters combat with access to passive Lightning from its starting setup. That means I do not necessarily need to distort the deck around a special multi-hit package just to remove those early charges.

Use the mechanic your deck already owns before drafting a new package for one Boss.
Lagavulin Matriarch

Orb output can stay reliable when normal attacks and Block are being weakened

The fight can reduce Strength and Dexterity, making ordinary attacks and defensive cards progressively worse. Orb output does not depend on those two stats in the same way, so an established Orb engine keeps doing its job while basic physical cards deteriorate.

A passive engine is valuable partly because it can ignore problems that attack- and Dexterity-dependent decks must solve directly.
Test Subject

Dark Orbs turn phase timing into stored damage

This fight is a good example of why I do not judge Dark by immediate output. A Dark Orb can spend an earlier phase accumulating damage, then be saved for a later phase or a window where the target is vulnerable to the Evoke. The important mistake is using the stored damage simply because it is available.

When a Boss has phases or restricted damage windows, Orb timing can matter more than raw card efficiency.
Reward-screen decisions

Defect Card Value Changes With the Orb Queue

These are the states where a card that looks like obvious synergy can still be the wrong reward.

Deck state 1

I have three Orb Slots but regularly finish turns with empty slots

The trap

“Capacitor is Orb scaling, so more slots must make the deck stronger.”

Better read

The current bottleneck is Orb generation, not capacity. I want reliable Channeling first. Extra empty slots do not produce passive damage, Block, or Energy.

Capacitor Ball Lightning Coolheaded Chill
Deck state 2

The queue is full almost every turn and I keep Channeling more Orbs

The trap

“I already have enough Orbs, so more Orb support is redundant.”

Better read

A full queue changes the question. Additional channels now create Evokes, and additional capacity can preserve useful Orbs longer. This is where Orb Slots, Focus, and queue control start multiplying an engine that already exists.

Capacitor Defragment Synchronize
Deck state 3

Frost already covers ordinary defensive turns

The trap

“This is a Frost build, so I should keep taking Frost cards.”

Better read

Defense may already be solved. If Bosses are living too long, I need damage conversion — perhaps Lightning for persistent pressure, Dark for stored burst, or even a physical package — rather than another copy of the role the deck already handles.

Coolheaded Darkness Ball Lightning
Deck state 4

A Dark Orb is already storing enough damage to finish a later phase

The trap

“I should keep Channeling because cycling Orbs is always good.”

Better read

The front of the queue now contains a win condition. I check every new Channel against the risk of Evoking it too early. Sometimes the correct Orb play is preserving the queue rather than accelerating it.

Darkness Dualcast Consuming Shadow
Deck state 5

I found one Claw but the deck still cycles slowly

The trap

“Claw scales, so I should start taking every zero-cost attack.”

Better read

One Claw is not yet an engine. I first need enough access and repeated cycles for cheap attacks to appear frequently. Until then, ordinary damage, defense, or Orb support can be much more important.

Claw Scrape All for One Coolheaded
Diagnose before drafting

What Does My Defect Deck Still Need?

Need immediate damage

Are early enemies surviving long enough that setup cards never get time to pay back their cost?

I prioritize damage that contributes immediately rather than adding another slow scaling layer.

Ball Lightning Rocket Punch Hyperbeam

Need reliable defense

Does one bad defensive draw still expose too much HP even though the damage plan is working?

Frost, direct Block, Weak, or another dense defensive answer matters more than further damage scaling.

Coolheaded Chill Null

Need Orb scaling

Is the Orb queue already active every turn but the passive output too small for longer fights?

Now Focus or other scaling can multiply activity that is already dependable.

Defragment Synchronize Biased Cognition

Need more Orb capacity

Am I repeatedly pushing useful Orbs out before I want to Evoke them?

Additional Orb Slots can create room to preserve the queue, but only if I can fill those slots productively.

Capacitor

Need Boss damage

Can the deck survive indefinitely but still take too long to end high-HP fights?

I look for damage conversion instead of adding more defense. Dark Orbs are one way to store several turns of value for a future burst window.

Darkness Consuming Shadow Claw

Need faster cycling

Does the deck contain strong cards but fail to reach them before the important turn passes?

Card access can be stronger than another payoff because it increases how often the existing engine actually appears.

Coolheaded Compile Driver Scrape

Need to survive setup

Are Powers and scaling cards strong on paper but costing too much tempo when first played?

I patch the setup turn instead of adding another slow Power. A deck only scales if it lives long enough to use the scaling.

Boot Sequence Null Coolheaded
Why promising Defect builds fail

Six Defect Build Problems I Check First

1

Too many Orb Slots, not enough Orbs

Capacity looks like scaling because the ceiling becomes larger, but empty slots are not output. If the deck cannot fill them quickly, the extra capacity may also delay the Evokes that were previously doing useful work.

2

Too much of one Orb type

The queue needs jobs, not visual purity. Filling every slot with Lightning can leave the deck unable to absorb a dangerous turn. Filling every slot with Frost can create a deck that survives but never finishes the Boss. I care about the problem each position is solving.

3

Dark Orbs are Evoked simply because they reach the front

Dark stores future damage. If the fight has a later phase or a better damage window, cycling the queue automatically can spend the deck’s best finisher before it is needed.

4

Focus is drafted before Orb activity exists

Multiplying a small or inconsistent engine does not repair the engine. I want enough Channeling and useful Orb uptime before spending too many rewards on scaling.

5

Claw is treated as a theme instead of a cycling requirement

Cheap attacks need to return to the hand repeatedly. If draw and deck speed are poor, stacking more zero-cost cards can create a low-impact deck that still waits too long between meaningful Claw turns.

6

Passive output hides a frontload problem

Defect can look powerful once the fight is established while still losing too much HP in the first few turns. A deck that wins turn eight but repeatedly collapses on turn two needs immediate stabilization, not a higher scaling ceiling.

Your current run

Defect is easier to diagnose by bottleneck than by Orb color.

Check whether the current problem is Channeling, Orb capacity, Focus, defense, card access, or damage conversion before adding another card that merely matches the existing theme.

Evaluate My Deck → Open Orb Build Guide →
Early Access versions

This page uses the current Main card dataset. Defect has several balance-sensitive cards, so a Beta change can move an individual reward before it changes the larger Channel, queue, Evoke, and scaling logic.

Check Main vs Beta →
Adjacent Defect questions

Defect Build FAQ

Should I remove Zap or Dualcast from a Defect deck?
I do not treat either starter as an automatic removal. Their value changes with the Orb engine. If Channeling and Evokes remain central, they can keep doing useful work; if the deck develops a faster non-Orb plan and stronger replacements, starter removal becomes easier to justify. I compare them with the weakest current draw rather than following a fixed removal order.
Can a Claw Defect deck still use Frost Orbs?
Yes. The damage engine and defensive engine do not have to share the same label. Frost can cover defensive turns while cheap attacks handle damage. The combination becomes a problem only when Orb setup, Claw cycling, and other packages all demand separate cards and the deck no longer reaches any of them consistently.
Does Defect need Focus to win with Orbs?
Not every useful Orb interaction requires a large Focus package. Focus is strongest when it multiplies several active Orb triggers, but queue timing, Evokes, stored Dark damage, and matchup-specific Orb utility can all matter independently. I take Focus because the current Orb engine benefits from it, not because every Defect deck must reach a fixed amount.
Is a larger Defect deck bad for Orb builds?
Deck size matters less than access to the cards that establish and control the Orb engine. A larger deck becomes a problem when Channeling, defense, or scaling appears too late. If additional cards solve specific fights while draw remains reliable, the raw card count is not the issue by itself.
Should Beta changes change which Defect build I play?
Sometimes individual card priorities move before the whole build structure changes. I keep the Main build logic separate from Beta balance changes and check the current Beta page when a run depends heavily on a recently changed card.