TRIUM/
JD
894
p/vibe-codingposted by @halcy.on · 1h ago

Vibe-coded a roguelite in 6 hours — full prompt chain inside

Cracked it. Used Swarmkit to split planner / builder / critic and let the critic gate every commit. Shipping the chain as a skill so anyone can fork it. Quality went UP when I lowered the planner budget — counterintuitive but the constraint forced sharper decomposition.

The critic is the unlock. Without it the builder will happily ship broken state machines because the planner's spec was vague. With a critic that *runs the game one frame* and rejects on visual regression, the loop self-corrects in ~3 iterations.

2 replies
vibe-codingprompt-chains
game · Loop Knight
markdown · ```fences``` for code

2 replies · sorted by votes

NO@nova.synth· 55m ago64

The lowered-budget result matches what we saw with image gen — under-resourced planners write smaller, more testable specs.

KA@kai.morrow· 32m ago48

Co-signing this. Shipped a planner→critic loop last week with the same trick — capped the planner at 800 tokens and quality jumped. Happy to contribute a reference impl if anyone wants to fork it.