A form that saves, without leaking everyone else's rows
Takes
40 min in 4 steps
Checked
19 Nov 2026
min
Your estimate is optional. Your review compares it with how long it took; nothing is scored.
A guestbook: people leave a name and a message, and the page lists the last 20. Simple, except that the most common real-world vibe-coding leak is exactly this setup: a database reachable from the browser with no rules on who can read or write what.
You'll needEither a free Supabase project, or Node.js with SQLite on your machine. The steps work for both; the pitfall matters most for Supabase. Prices checked this month are on Tools.
Spec the data first
Step 1 of 4, about 5 min
Add to SPEC.md: one table messages with id, name (max 40 chars), body (max 280), created_at. Who can read: everyone. Who can insert: everyone. Who can update or delete: nobody from the browser.
The part of a video worth watching for this step
YouTube, Claude. Published Sep 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
Build the form and the list
Step 2 of 4, about 15 min
Run it, post two messages, reload. Commit.
Paste this to your agent
Following SPEC.md, add a guestbook form and list of the last 20 messages. Use <Supabase / SQLite>. Validate lengths on the server or in the database, not only in the form.
The part of a video worth watching for this step
YouTube, Tech With Tim. Published Jul 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
Try to break it from the browser
Step 3 of 4, about 10 min
Open the browser's developer tools. If the page talks to Supabase directly, the URL and anon key are visible there, and that's normal. What must not be possible is using them to delete rows. Ask the agent: "Show me the exact request someone could send from the console to delete a message, and what our database answers." Then try it.
The part of a video worth watching for this step
YouTube, AI Engineer. Published Nov 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
the usual mistake
Row Level Security off. With it off, the public anon key can read and write the whole table. In 2025 a researcher found 170 of 1,645 apps built on one popular builder exposing data this way (CVE-2025-48757). It happened to us in INC-14, "Secrets in git, across dozens of repos".
Lock it and re-test
Step 4 of 4, about 10 min
Repeat the delete attempt. It should fail. Posting a message should still work.
Paste this to your agent
Enable Row Level Security on messages with a select policy for everyone and an insert policy for everyone. No update or delete policies. Show me the SQL before running it.
The part of a video worth watching for this step
YouTube, Mikey Vibe Coding. Published Apr 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
Check and ship
The whole ticket
From the browser console (or curl), try a delete as an anonymous user.
# Supabase example, with your project URL and anon key
curl -X DELETE 'https://<project>.supabase.co/rest/v1/messages?id=gt.0' \
-H 'apikey: <anon key>' -H 'Authorization: Bearer <anon key>'
It passes whenNo rows are deleted (Supabase answers with an empty result or an error), and the messages are still on the page.
Submitting the form stores a row; reloading shows it.
Nobody can delete or edit other people's messages from the browser console.
If you use Supabase: Row Level Security is on for the table, with one policy for read and one for insert.
No server checks your work in this version: you mark it, and your review says "Checked by you". Graded checks are planned for Plus.