greenlıt

Guide · Copy and paste

Vibe coding security prompt: paste this into Lovable, Bolt or v0

AI builders write the code you asked for. Unless you ask, they rarely lock it down. This prompt asks your builder to fix the eight problems that show up most often in AI-built apps. Paste it in before you launch, then check from the outside that the fixes are really there.

Updated 19 November 2026

The prompt

Review this app for security before launch and fix what you find. Work through each point, then tell me what you changed and what you couldn't change. 1. Secret keys: make sure no secret key is in the frontend code or in any file the browser downloads. That includes Stripe secret keys (sk_), OpenAI or Anthropic keys, and the Supabase service_role key. Move every call that needs a secret key into a server or edge function and keep the key in a server-side secret. 2. Database rules: turn on Row Level Security on every Supabase table. Write policies so a user can only read and change their own rows. Remove any policy that is just "true" for everyone, unless the table is meant to be fully public, and tell me which tables those are. 3. Sign-up: don't let a rule that says "signed-in users" stand in for "this user owns this row". Every policy must check whose data it is. 4. File storage: make storage buckets private unless they hold files everyone is meant to see. Serve private files with signed links that expire. 5. Server functions: every edge function or API route must check who is calling and whether they're allowed to do what they ask before it charges, emails, deletes or returns data. 6. Payments: if the app gets Stripe webhooks, verify Stripe's signature on every one, and ignore any "paid" message that fails the check. 7. Source code: don't publish source maps, .env files or the .git folder on the live site. 8. Headers and leftovers: add basic security headers (frame protection with frame-ancestors or X-Frame-Options, a Content-Security-Policy, X-Content-Type-Options: nosniff). Remove test-mode payment keys, calls to localhost, placeholder titles and anything that hides the site from search engines. Don't change how the app looks or behaves for real users. If a fix would change behaviour, ask me first.

Why each line is there

Secret keys are the most common problem we see: anything your site sends to the browser is public, and a secret key there lets anyone charge cards, run up your AI bill or read your database. The Supabase anon key and a Stripe pk_ key are meant to be public. Secret ones never are. If one already leaked, rotate it first.

Database rules decide what a stranger can read with your public key. A table without Row Level Security is open to anyone. How to check your RLS.

Storage, server functions and webhooks are where a working app quietly trusts whoever calls it. Source maps and headers are cheap to fix and easy to forget. Leftovers don't leak anything, but they make a launch look broken.

Don't take the builder's word for it

An AI builder will often say "done" when only part of the fix landed, or put a key back while fixing something else. Check from the outside, the way a stranger would. Greenlit reads what your live site actually sends, grades it from A to F, and writes a fix prompt for anything still wrong. Run it after every round of fixes.

From just a link, Greenlit checks secret keys, source maps, headers and launch leftovers. To check your database and storage rules, prove the app is yours first: add the tag the site gives you, or run npx greenlitlab yourapp.com --mine on your own computer. Points 5 and 6 need you or your builder to look; no outside check can see them.

Check your app in 30 seconds

Paste your app's live address. Free, no sign-up, and it reads only what every visitor already sees.

Check your app

More guides