Define the Lane Breaker encounter
A side-scrolling brawler prompt should state how horizontal position and lane affect a hit. Lane Breaker is a fictional ten-cell arena with near and far lanes. The player starts at x1 in the near lane with five health. A two-health Grunt waits at x4 near; a three-health Bruiser waits at x8 far.
The player chooses one action per beat: Step one horizontal cell, Shift Lane at the same x-coordinate, Jab an adjacent enemy in the same lane for one damage, or Guard. Guard blocks one enemy attack during the current beat and then expires. Enemies in another lane do not move or attack the player.
After the player action, defeated enemies are removed. Each surviving enemy in the same lane moves one cell toward the player when farther than one cell away. If already adjacent, it advances its attack counter. Every second adjacent beat it attacks for one damage, then resets its counter.

Resolve attacks, movement and enemy timing
This order lets a Jab defeat an enemy before its enemy phase. A lane shift changes only the lane, not x-coordinate or health. A Step cannot cross the arena bounds. Jab is illegal unless an enemy is one horizontal cell away in the same lane; an illegal action changes no state.
The player wins after defeating both enemies before beat 12. The run ends in a loss at zero player health or when beat 12 resolves without both enemies defeated. Restart returns each fighter to the start positions and health, resets enemy counters, Guard and beat number.
The first encounter has no combo chains, knockback, pickups, screen transitions or enemy randomization. This keeps lane choice and spacing visible before additional brawler systems are introduced.

Trace the example
A near-lane opening can begin with the player stepping from x1 to x2. The Grunt at x4 is two cells away, so during enemy phase it moves to x3. The next beat the player Jabs from x2, dealing one damage while adjacent. The Grunt remains alive at one health; its first adjacent counter advances but it does not yet attack.
On the following beat a second Jab removes the Grunt before its enemy phase, so no further counter or attack resolves. The player can then shift to the far lane at the same x-coordinate and approach the Bruiser. This trace illustrates the order rule but does not claim the encounter was played.
A future build log should include lane, x-position, action, enemy health and counter before and after the enemy phase, Guard state, and player health. It should also test Jab across lanes to confirm that visual overlap does not create an invalid hit.

Write the six prompts
Use one prompt per design decision so later checks have a clear source of truth. These drafts describe Lane Breaker; they have not been run and do not represent a generated playable game.
Prompt 1: place lanes and enemies
Create a 10-cell side-scrolling arena with near and far lanes. Player starts x1 near with 5 HP. Put a Grunt at x4 near with 2 HP and Bruiser at x8 far with 3 HP.Prompt 2: define movement and attacks
Player actions: Step one horizontal cell, Shift Lane at same x, Jab an adjacent same-lane enemy for 1 damage, or Guard. Reject out-of-bounds Step and non-adjacent/cross-lane Jab without state change.Prompt 3: order enemy movement
Resolve each beat: player action, remove defeated enemy, then enemy phase. Same-lane enemy moves one cell closer if distance>1; if adjacent, count one adjacent beat. Different-lane enemies hold.Prompt 4: set attack cadence and Guard
An adjacent enemy attacks for 1 every second adjacent enemy phase, then resets its counter. Guard blocks one incoming attack this beat and expires. Track counters explicitly.Prompt 5: define match outcomes
Win after both enemies are defeated before beat12. Lose at 0 player HP or after beat12 without victory. Restart restores positions, health, counters, Guard and beat.Prompt 6: prepare future checks
For future checks log lanes, coordinates, action, HP, counters, enemy phase and Guard. Check cross-lane Jab, adjacency counter, Guard, defeat-before-enemy-phase, boundary, loss and reset. 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 Lane Breaker. See Free AI game maker for workflow context only.
Prepare future build checks
Capture lane and x-coordinate at each action, then inspect enemy movement and attack counters. Verify cross-lane attacks are rejected, Guard blocks only one due hit and a defeated enemy skips its phase. 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 |
|---|---|---|
| Jab legality | Adjacent and same lane only | Player/enemy coordinates and lane |
| Enemy movement | Moves one cell when farther than one | Before/after x-position |
| Attack cadence | Attacks every second adjacent phase | Counter and health |
| Guard | Blocks one attack then expires | Guard state and hit count |
| Win/loss/reset | Two defeats win; HP/beat limit lose | Outcome and reset snapshot |
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 side-scrolling brawler prompt define?
Define lanes, move range, attack range, enemy timing, damage, guard and round end conditions.
Can Jab hit an enemy in another lane?
No. The target must be adjacent in the same lane.
How often does an adjacent enemy attack?
Every second adjacent enemy phase; its counter resets after attacking.
Were these brawler prompts tested in a playable game?
No. Lane Breaker is a fictional rules example and its turn trace is not observed gameplay.
What does Guard block?
It blocks one incoming enemy attack during the current beat, then expires.


