메뉴
Find which cards in a SWU set are reprints of earlier-set cards and add the mappings to AppCore/SWU/Overrides.php. Use when a new set is released and its reprints need to be aliased back to their earliest printing for deck stats. Takes a set code (e.g. ASH, LAW, SEC).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | swudeck-reprint-overrides |
| description | Find which cards in a SWU set are reprints of earlier-set cards and add the mappings to AppCore/SWU/Overrides.php. Use when a new set is released and its reprints need to be aliased back to their earliest printing for deck stats. Takes a set code (e.g. ASH, LAW, SEC). |
AppCore/SWU/Overrides.php (CardIDOverride) aliases a reprinted card's CardID back to the
CardID of its earliest printing, so deck stats treat reprints as one card. This skill
finds a set's reprints and appends the case lines.
A card is a reprint of an earlier card when they share the exact same:
null and "" as equivalent — the data is inconsistent across sets)Ignore tokens (Shield, Experience, Battle Droid, Clone Trooper, TIE Fighter, X-Wing,
The Force, Spy, Advantage, etc.). Filter by type.data.attributes.value == "Token".
Token IDs also diverge between systems (SWUSim SOR_T02 vs SWUDeck SOR_002), so they
must not go in these overrides anyway.
SWUSim/GeneratedCode/cardArrayCache.json → cardArray is the full multi-set card DB.
Each entry has: id (CardID like ASH_122), title, subtitle, cost,
aspects.data[].attributes.name, expansion.data.attributes.code, and
type.data.attributes.value. For non-token cards the SET_NNN id format is identical
to what SWUDeck's overrides use, so the id can be used directly.
Derived from each expansion's publishedAt. Current order (oldest → newest):
SOR, SHD, TWI, JTL, LOF, IBH, SEC, LAW, TS26, ASH. The script re-derives this from the
data so it stays correct as sets are added.
python3 .claude/skills/swudeck-reprint-overrides/scripts/find_reprints.py ASH
case lines and the full printing chain for each hit so you
can confirm the target is genuinely the earliest.case lines to AppCore/SWU/Overrides.php, just before default: return $cardID;,
following the existing case "XXX_NNN": return "YYY_NNN"; //Card Name format.Use when debugging a specific SWUSim in-game bug or unexpected behavior tied to a real game (e.g. "game 2619 auto-resolves this leader ability wrong", "why did this prompt appear", "this ability should have auto-passed", "the shield popped when it shouldn't"). For reproducing and root-cause-fixing a live-game defect from its saved gamestate.
Use when starting a NEW SWU set to generate its consolidated SWUSim/docs/<set>-implement.md plan (for swusim-implement-set-plan to drive). Scans the generated card dictionaries, classifies every card, surveys for unbuilt core mechanics (hard-stops if found), then batches needs-work cards autonomy-first. Generate-only; one set abbreviation as input.
Use when implementing SWU card abilities — looks up card text, writes all DSL tests first, then self peer-reviews against the CR + game logic + card data and implements; only stops for the user on a card it can't verify to 98% alone. Supports single cards and batches.
Use when the user wants to drive a whole multi-batch SWUSim implementation plan doc (e.g. docs/<set>-complex-plan.md) to completion in one session — "run/execute the <set> plan", "work through the remaining phases". For many card batches across phases at once; for a single batch use swusim-implement-card.
Use when asked to verify a SWU set is "card complete" / review a set for implementation gaps (e.g. "is JTL card complete?", "validate the SOR set", "what's left in LOF?"). Runs two independent completeness checks — a dictionary-vs-Done-list diff AND an inverse-stub sweep that proves every trigger stub has a real handler — classifies each finding as a real gap or a false positive, and reports. Read-only validation; hand real gaps to swusim-implement-card.
Use at the end of a SWUDeck (NOT overall TCGEngine work) working session to run a short retro, capture durable lessons, and hand off cleanly. Invoke when the user says they're wrapping up, asks to "close the session", "run the retro", or asks "what were the lessons learned this session".