card-skills

Define constraints first (grave state, turn, phase), query cards.cdb for cards matching the starter's attribute and race, read each card's full effect text, then build sequences step by step validating legality at each step. Rank results by end-field strength and consistency.

Check each step for summon legality, activation conditions, card source validity, resolution order, phase restrictions, and resource accounting. Common pitfalls include assuming grave contents never sent there, using searched traps the same turn, and miscounting Link material values.

A hand trap must activate from the hand during the opponent's turn to interfere with the opponent; all three conditions are required. Cards that only self-summon from hand, only search, or need a monster on field to activate are excluded.

Yes, the Python scripts query a local cards.cdb SQLite database with datas and texts tables containing card IDs, types, attributes, races, levels, and effect text. The database file must exist in the combo directory or a specified path.

Engine patterns are recurring resource loops shared across archetypes, such as token-plus-tuner synchro ladders, grave-fusion piles, and trap recursion loops. Each pattern documents its one-card entry point, end field, and the choke point where one interruption stops the line.