Vibe-Coder Bug Roulette is a browser toy for the post-AI coding era. Pick your stack — Cursor, Lovable, Replit Agent, v0, Bolt, or Claude Code — spin the wheel, and the wheel tells you which production bug you are statistically about to ship today. Each segment is a real bug archetype paired with a probability stat that we did, in fact, calibrate by vibes. Some are rare. Some are legendary. All of them have happened to somebody.
The rules are simple. Pick a stack to enable the spin. Hit SPIN. The danger meter fills to the bug's doom percent, the description types itself out, and a result card lands ready to screenshot. Keep spinning to grow your sprint bag — your session keeps the worst (highest-probability) bug you have rolled, and the running doom score is your you-are-this-doomed total. There is no win condition; the game is rolling something funnier or worse and posting it. Land a legendary and the wheel makes you regret it.
The premise is not that AI coding is bad. The premise is that vibe coding — shipping AI-generated code without reading it — has a different set of failure modes than typing code yourself. Cursor's confident rename touches every file except the one that matters. Lovable's preview is fine and prod silently 401s. v0's screenshot is beautiful at 1440 and a mood board at 375. The roulette is a way to laugh at the pattern, screenshot the result, and — if you actually want to de-risk your AI-coded app — wander over to the Vibe-QA assessment next door.
Related reading: Vibe-QA assessment · SimQA management sim · Flaky or Fixable triage game · Vibe coding and the QA gap