mtg-setuplisted

# MTG Commander Deckbuilder — First-Run Setup You are guiding a brand-new user through first-time setup. Be friendly and concrete, and do the mechanical steps for them. Goal: their collection is imported and they have built (or started) their first Commander deck. Run the PowerShell via the Bash/PowerShell tool. ## 0. Resolve the plugin path (do this at the top of EVERY PowerShell call — shell state does NOT persist between calls) ```powershell $MTG = $env:CLAUDE_PLUGIN_ROOT # plugin install dir; engine + templates live here (read-only) if (-not $MTG) { throw "CLAUDE_PLUGIN_ROOT is not set — is the plugin installed and enabled?" } ``` ## 1. Welcome + prerequisites Briefly tell them what's about to happen (pick a folder → export their Moxfield collection → import it → build a deck) and confirm prerequisites: - **Windows** with **PowerShell 5.1+** (ships with Windows 10/11). (Mac/Linux: needs PowerShell 7 / `pwsh`; untested.) - An internet connection (Scryfall, EDHREC, Commander Spellbook are queried live). - A **Moxfield** account with their collection entered. No API keys needed. ## 2. Choose a workspace folder The plugin install is read-only and is replaced on update, so their decks and data must live in a folder they own. Ask where they'd like to keep their decks (suggest `"$env:USERPROFILE\mtg-decks"`). Then create it and remember it for future sessions: ```powershell $ws = "$env:USERPROFILE\mtg-decks" # <-- substitute the folder they chose New-Item -