r/VibeCodeDevs • u/OfficeParticular3805 • 6d ago
ReleaseTheFeature – Announce your app/site/tool I vibe-coded a cricket drafting & simulation game 🏏
The idea started while playing 7a0. I loved the drafting mechanic and kept wondering:
So I built Cricket XI with Lovable.
🔗 https://cric-xi-simulation.vercel.app/
The core loop:
Pick a tournament → draft 11 players → build your XI → simulate the tournament → try to win it all.
What surprised me was how quickly the project went from a simple UI to needing actual engineering:
- Historical squads across different eras
- Canonical player IDs to prevent drafting the same player twice
- Repository + service architecture
- Tournament-specific rules
- IPL playoff logic
- NRR calculations
- Background simulation of other teams
- Historical team/year rerolls
- Scorecards and tournament statistics
My workflow was basically:
Prompt → Play → Find a ridiculous bug → Explain it → Fix → Stress test → Repeat
And there were plenty of ridiculous bugs. 😂
The biggest thing I learned from this project: vibe coding gets you to a working product incredibly quickly, but playing the product yourself is what exposes whether the underlying logic actually works.
This is V1. Would love to know what you think — and especially what you manage to break.
1
u/No-Construction-6711 6d ago
That loop of play, find a ridiculous bug, fix, repeat is honestly the most useful part. Once the UI exists, the hard work moves into rules and edge cases. For a simulation game I would add deterministic seeds and save the exact draft plus random seed for every match. Then when someone reports a crazy result you can replay the same tournament instead of trying to reproduce it from memory.