Define the Pouch of Sparks round
A bag-building prompt should say how many tokens are drawn, when they are discarded and how an upgrade enters future draws. Pouch of Sparks is a fictional four-round boss encounter. The player begins with three health and zero coins; the boss has six health.
The starting bag has two Strike tokens (one damage each), two Guard tokens (block one incoming one-damage boss attack this round) and two Coin tokens (gain one coin). Each round draw three tokens without replacement and resolve all three, then discard them. If three or fewer remain in the bag at the next round, shuffle the discard into it before drawing.
At the end of each round the boss attacks for one damage unless a Guard was played. Between rounds the player may buy at most one token: Strike+ costs one coin and deals one damage; Heavy costs two coins and deals two damage. A purchased token goes to discard and cannot be drawn until reshuffled.

Track tokens through bag, hand and discard
This lifecycle matters: a token in discard is not immediately available. At the round boundary, first resolve the boss attack, then choose a market purchase, then check whether the next draw needs a reshuffle. The market item is added to discard before that shuffle, so it can enter the next round's draw when the bag has three or fewer tokens.
The player wins when the boss reaches zero health by the end of round four. The player loses at zero health or when the fourth round resolves with the boss alive. Restart restores the six-token bag, clears hand/discard, resets coins and health, and restores the boss.
The prompt does not promise that every shuffled draw is balanced. A future build should display bag, hand, discard and purchase zones separately so the token path can be inspected.

Trace the example
In a fictional first-round draw of Strike, Coin, Guard, the player deals one boss damage (6→5), gains one coin and blocks the boss's one damage, staying at three health. The three tokens then move to discard. Between rounds, the player spends one coin on Strike+ and places it in discard.
Only three tokens remain in the bag, meeting the three-or-fewer reshuffle condition. Before the next draw, the discard—including Strike, Coin, Guard and Strike+—is shuffled into the bag. The upgrade is now eligible for a later draw, but it was not available during round one. This separation is the core bag-building feedback loop.
This is a fictional state trace, not a played encounter or balance finding. Random draw order may differ in a real implementation; the rules and token zones should be tested independently of any single outcome.

Write the six prompts
Use one prompt per design decision so later checks have a clear source of truth. These drafts describe Pouch of Sparks; they have not been run and do not represent a generated playable game.
Prompt 1: create combat state and starter bag
Create a boss encounter with boss6 HP, player3 HP, coins0 and 4 rounds. Starting bag: two Strike(1 damage), two Guard(block one 1-damage attack this round), two Coin(+1 coin).Prompt 2: define draw and discard
Draw three tokens without replacement each round and resolve all three. Then move them to discard. If three or fewer remain in bag before next draw, shuffle discard into bag first.Prompt 3: add boss attacks and market
At round end boss attacks for1 unless Guard was played. Between rounds buy at most one token: Strike+ costs1 coin/deals1 or Heavy costs2/deals2. Put purchase in discard before reshuffle check.Prompt 4: resolve win/loss
Win when boss HP reaches0 by end of round4. Lose at player HP0 or after round4 with boss alive. Do not let health or boss HP fall below0.Prompt 5: show token zones and reset
Show bag, drawn hand, discard, coins, health and boss HP. Restart restores starting bag and state.Prompt 6: prepare future checks
For future checks log draw source, token effect, zone transition, purchase, reshuffle, attack and health. Check draw count, discard timing, upgrade entry, Guard, deadline and Restart. Do not claim tests passed without a build.SEELE’s official page describes general plain-English prompting, a playable first version, browser testing and refinement; it does not verify Pouch of Sparks. See Free AI game maker for workflow context only.
Prepare future build checks
Record each token's zone at round boundaries. Test three-token draw, discard movement, reshuffling with fewer than three, a market purchase entering discard, Guard and the final round outcome. These are future checks, not passed tests. Record the before and after state so a later build can be compared with the specification.
| Future check | Expected rule | Evidence to capture |
|---|---|---|
| Draw | Three without replacement | Bag and hand counts |
| Discard | Resolved tokens move after round | Token zone before/after |
| Reshuffle | Occurs when three or fewer remain | Bag/discard counts and order |
| Purchase | At most one affordable token goes to discard | Coins and token location |
| Round end | Guard, boss attack and deadline resolve correctly | Health, boss HP and round |
No real game run, browser test or measured result is available for this fictional example. The illustrations are original concept art and are not screenshots.
Frequently asked questions
What should a bag-building prompt define?
Specify token effects, draw count, discard timing, reshuffle rules, upgrade purchases and the win deadline.
When can a purchased token be drawn?
It enters discard first and becomes available after the discard is shuffled back into the bag.
How many tokens are drawn per round in Pouch of Sparks?
Three tokens are drawn without replacement each round.
Were the bag-building prompts tested in a playable game?
No. Pouch of Sparks and its token trace are fictional design material, not observed gameplay.
How does Guard work?
It blocks the boss's one incoming damage for the current round, then leaves play with the other resolved tokens.


