Suggestions
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
What this surface is
Suggestions is the problem-driven improvement surface. Its own description:
DeckScope diagnosed your list against the active meta and your collection. Each problem below opens a curated set of swaps, ranked by expected impact and weighted by what you can build today. Apply individually, or stage them and ship as one revision.
The shape is problems first, cards second. You do not get a flat “good cards” list — you get a ranked list of problems, each expanding into candidate moves that address that specific problem.
Where to find it in the app
Open a deck in Deck Lab, then Analytics ▾ → Suggestions. With no deck selected: “Select a deck from the Select Deck tab to generate suggestions.”
Entitlement
“Deck suggestions are a Slifer+ feature.” Without it the surface shows the upgrade prompt instead of the workstation.
KPI strip
| KPI | Sub-line |
|---|---|
| Problems diagnosed | how many dimensions, plus a high / medium / low breakdown |
| Candidate moves | across how many problems, split into owned and need-buying |
| Readiness Δ if applied | weighted by tournament evidence |
| Avg. confidence | averaged over the top 5 candidates |
Problems
“Problems & their fixes — highest severity first. Each tile expands to a ranked candidate table.” Severity is one of three levels, shown as High / Med / Low. Each problem tile carries a candidate count and its own Readiness Δ.
Candidate table
| Column | What it holds |
|---|---|
| Pri | Priority rank within the problem |
| Candidate | The card being suggested |
| Replaces | The card it swaps out, or ”— add only” |
| Roles | Role chips — Engine, Handtrap, Floodgate, Extender, Search, Recovery |
| Expected impact | Impact bars for the affected dimensions |
| Confidence | A confidence meter; a gold ring marks top-tier confidence |
Each row is an Add, a Remove, or a Swap. Sort the table by Confidence, Priority, Impact, or Owned-first. Two bulk controls sit above it: Apply package (take the whole set) and Stage top N.
Rows you do not own offer Stage buy rather than a direct apply.
Staged moves
Staging is the “build a revision, then ship it” path. The cart tracks:
- Cards in / Cards out
- Buy cost for anything staged that you do not own
- Readiness Δ for the staged set as a whole
- An Activity log of what was staged and what was applied
Apply staged commits the whole set at once; Discard staging throws it away. Empty state: “No moves staged — stage candidates from the tables above to preview the impact of a revision.”
Related workflows
Related references
- Quick Analysis — the diagnosis Suggestions acts on
- Analysis Lab — deep, saved analysis runs
- Deck Lab — the workspace this sits inside
- Market — where staged buys end up