NFL Pick’em for our decade-old friend group. Full-stack, real-time scores, the whole nine.
v0 + Claude Code + Codex CLIMy friends and I have had an NFL picks pool for over a decade. Every year we'd use a very Windows-95-esque spreadsheet then eventually the (functional but annoying) Yahoo Fantasy app. In 2025, I built the app we'd always wished for.
Real-time ESPN scores, betting lines, season-long stats, automated winner tracking. The whole nine. Full-stack with Next.js, Supabase, and the ESPN API pulling live game data. Six of us use it every Sunday during the season and honestly it's become part of the tradition now.
Live game day view — scoreboard with real-time ESPN scores, betting lines, and pick status for each player
I will say though -- the tiebreaker logic almost killed the project. At least for me, mentally. Claude Code kept refactoring it into something that technically worked but handled edge cases wrong. So I finally brought in Codex as the reviewer agent and had it sort out the tiebreaker while Claude moved on to other features. Two AI agents, same codebase, different problems. That was the first time I realized multi-agent workflows weren't just theoretical -- they were practical.
Season-long standings or leaderboard showing all 6 players, win/loss records, and tiebreaker stats
I'd never used a database or an API before, so there were a lot of hours in this one. If I built it again, I'd fight the urge to solve every edge case at once. The tiebreaker nearly killed the project because I didn't know when to stop refining and start shipping. But in the end, we have our own app that everyone loves, because I can just do that now.
Diagram or side-by-side terminal screenshot showing the two-agent workflow — Claude Code on features while Codex reviews tiebreaker logic
Optional