Hardening a Replit AI MVP for Production

A vibe-coded Replit app can survive a demo. Production asks different questions. What happens when two users hit the same endpoint? Can one user read another user's records? Are Stripe live keys separated from test keys? What stops an LLM call from looping until the bill hurts? Before you share the link outside your team, harden the app around a few boring files and rules. Boring is good here. 1. Start with replit.md Replit's agent needs persistent instructions. Without them, eac...