From hobby to real world: integrating the hard stuff with agents

Summary

The post documents building a production-oriented leaderboard for open-source Stripe Projects applications, where users submit projects, share links, and vote. Unlike an earlier transcription app, this project required authentication, multiple database tables, hosting, and controls limiting unauthenticated users to one vote per project. The agent initially selected Supabase for database and auth and Vercel for hosting, then added Upstash Redis after an in-memory rate limiter proved unsuitable for serverless enforcement. Supabase's two-emails-per-hour authentication limit prompted a human-directed migration to Clerk, after the agent proposed an unsuitable Twilio solution. The resulting MVP used five resources across four providers, took more than a day, and received separate security and performance audits before review.

Takeaways

1. 1

   An in-memory rate limiter was unsuitable for enforcing voting integrity on the serverless architecture, so the vote flow required server-side enforcement through an atomic database function and Upstash Redis.

2. 2

   Supabase Auth permitted only two emails per hour for the project; replacing it with Clerk avoided setting up a custom SMTP or email service for the stated authentication need.

3. 3

   Detailed requirements covering data models, styling, and UX reduced iteration, while the initial simplicity bias led the agent to choose a database-and-auth provider that later required migration.