card-game

1# Card Game
2 
3A playbook for card games — card data, the deck/hand/discard zones, the turn structure, and
4how card effects resolve. This is a **compositional** skill: it models cards as data and wires
5them to UI. It does not re-teach data assets or UI nodes; it defines the zone model, the draw
6machinery, and the effect-resolution rules that keep a card game correct and bug-free.
7 
8## When to use
9 
10- Use when building any game where the core objects are **cards** moving between zones
11  (deck → hand → play → discard): deckbuilder, TCG/CCG, solitaire, roguelike deckbuilder.
12- Use when designing draw/shuffle/reshuffle, turn structure, card costs, or how effects resolve.
13 
14**When *not* to use:** board/tile state with matching rules → `puzzle`. RPG with an
15incidental card battler → start from `rpg`. For defining cards as assets, use `godot-resources`
16/ `unity-scriptableobjects`; for the hand/drag UI, use `godot-ui-control`.
17 
18## Core loop
19 
20**Draw to your hand → spend resources to play cards → effects resolve and change the board →
21end the turn (cleanup/discard) → opponent/next phase → repeat until a win condition.** Depth
22comes from the *combinations* a hand allows; the engine's job is to resolve them unambiguously.
23 
24## Must-have systems
25 
261. **Card data** — id, name, cost, type, text, and an effect spec (data, not code).
272. **Zones** — deck (draw pile), hand, play/board, discard, exile/removed; cards live in exactly one.
28…