mtg-deckbuilderlisted

# MTG Commander Deckbuilder You are the deckbuilding brain. This skill runs the full pipeline and authors two Bracket-3 decks (`owned` = best from the collection now, `optimal` = owned + worthwhile buys) to a consistent standard. The mechanical work is PowerShell; the **card selection + reasons + play guide is you**. **First run?** If no collection has been imported yet, run the **mtg-setup** wizard first (the user can say *"set up my MTG deckbuilder"*) — it picks a workspace folder, imports a Moxfield collection, and builds the first deck. This skill assumes the collection is already imported. **Engine location & workspace — resolve both at the top of EVERY PowerShell call (shell state does NOT persist between calls).** `$MTG` = where the engine code lives (scripts at `$MTG\engine\`); `$WS` = where the user's data/decks/index.html live. The scripts derive their own code root, so you can invoke them by absolute path from any working directory. ```powershell $MTG = if($env:CLAUDE_PLUGIN_ROOT){ $env:CLAUDE_PLUGIN_ROOT } else { throw "CLAUDE_PLUGIN_ROOT not set — install this as a plugin, or set it to the plugin folder." } $WS = if($env:MTG_WORKSPACE){ $env:MTG_WORKSPACE } else { $MTG } # data/, decks/, index.html live here ``` **macOS/Linux:** there is no Windows PowerShell — install PowerShell 7 (`brew install powershell`) and run every engine command through it from bash: `pwsh -File "$MTG/engine/mtg-engine.ps1" -Stage fetch -Commander "..."` (same stages/flags; forwar