llms.txt
Compare with other sites' llms.txt files →# Vibe Coding Checklist
> A free, two-minute self-check for apps built with AI (Lovable, Bolt, Cursor, Claude, Replit, v0). Ten yes-or-no questions about the back-end systems an AI-built app needs before real users, a personal fix list, and a copy-paste prompt for each gap. Made by Andrew Adams, a UX design leader in Seattle who builds products with AI coding agents. A guide, not a professional security audit.
## Pages
- [The check](https://vibecodingchecklist.com/quiz/): Ten yes / not sure / no questions; the result lists only the gaps, each with a prompt to give your AI.
- [The checklist](https://vibecodingchecklist.com/checklist/): All ten items on one printable page, with plain-English explanations and common questions.
- [The Lovable launch checklist](https://vibecodingchecklist.com/lovable/): Where each of the ten lives in Lovable (Cloud → Database, Secrets, Storage, Usage, Logs), plus the Quick scan, Deep scan and security review to run before publishing. Based on Lovable's docs, checked October 2026.
- [The Bolt launch checklist](https://vibecodingchecklist.com/bolt/): The Publish-menu security audit, the database Security page ("Ask Bolt to fix"), Secrets, public vs private storage buckets, pausing of unpublished projects, and why Version History doesn't restore data. Based on Bolt's docs, checked October 2026.
- [The Cursor and Claude Code launch checklist](https://vibecodingchecklist.com/cursor-claude-code/): The ten checks for code-editor agents, plus Claude Code's /security-review and .env deny rules, the claude-code-security-review GitHub Action, Cursor's Bugbot and Security Reviewer, and why .cursorignore isn't a security boundary. Checked October 2026.
- [The Supabase launch checklist](https://vibecodingchecklist.com/supabase/): RLS on every table, the Security Advisor, publishable vs secret keys, auth email rate limits and custom SMTP, storage policies, free-plan pausing (7 days, restorable for 90), backups and monitoring. Based on Supabase's Production Checklist, checked October 2026.
- [The Firebase launch checklist](https://vibecodingchecklist.com/firebase/): Replacing Firestore test mode rules, which API keys are safe to ship (and which aren't), roles via custom claims, Spark-plan auth email limits, Storage rules and the Blaze requirement, budget alerts vs spend caps, Firestore backups and monitoring. Based on Firebase's security checklist, checked October 2026.
- [The Ship Check](https://vibecodingchecklist.com/ship-check/): A step-by-step security check (coming soon).
- [Resources](https://vibecodingchecklist.com/resources/): Essays and case studies behind the checklist.
## The ten items
1. Your data: what things are and how they connect (the data model).
2. Accounts: sign up, sign in, password reset, and account deletion.
3. Permissions: private data is checked on the server, not just hidden in the interface.
4. Database rules: access rules enabled on every table (row-level security in Supabase, security rules in Firebase).
5. Secret keys: no secret keys in front-end code or public repos; rotate any that leaked.
6. When things break: half-finished actions such as a payment without a saved order.
7. What leaves your app: emails, push notifications, payments and webhooks, tested without reaching real people.
8. Uploads: storage privacy, size and file-type limits, checked on the server.
9. Hosting and cost: what the app runs on, the monthly bill, spending alerts, and what breaks at 10x usage.
10. Knowing when it breaks: alerts that check what users actually experience, and expiring keys and domains.
## Source
- [Vibe coding gets you a demo. Here's what it takes to ship a product.](https://andrewadamsdesigns.com/writing/from-prototype-to-product/): The essay the checklist comes from, with the real mistakes behind each item.