Vibe Coder · Unit 13: Login and Data With Supabase · Project
Milestone 13 of 23
Sign-in and saved data
Accounts and a database behind your app.
One product, built one milestone at a time
Vibe Coder has one project. You pick an idea in Unit 1 and every unit adds a piece to it, until the last unit launches it. Every milestone ends with a push to your own GitHub repository. Until now your app forgets everything and knows nobody. This milestone gives it accounts and a database with Supabase, and makes sure each person can reach only their own rows.
- 1Your builder’s kitA one-line product idea, your role, and five working accounts.
- 2A fact-checked product briefOne page on your idea, tested against how the models really behave.
- 3Your product project in ClaudeA project with instructions and files, and your first real piece of work from it.
- 4A brand kit and research fileA name, images and market research for your product, with a second opinion.
- 5Your prompt libraryThe prompts you will reuse to build the product, each one tested.
- 6Your product specThe problem, the people, the first version and how you will measure it.
- 7A clickable prototypeA version people can click through, shown to three of them.
- 8A working first draftYour product generated from the brief, with sign-in and data, in your own GitHub repository.
- 9The first working versionYour app running on your computer, built with Claude Code.
- 10Your Claude Code setupProject instructions, a custom command and a skill made for your app.
- 11One AI featureA feature in your app that calls a model, with its key kept safe.
- 12A connected assistantClaude or ChatGPT connected to a tool you already use, with the right permissions.
- 13Sign-in and saved dataAccounts and a database behind your app.
- 14Your app, liveOnline at its own address, updating every time you save.
- 15Your product’s back officeThe automatic jobs behind your product, as tested workflows in GitHub.
- 16An agent that works for your productOne agent with narrow tools, limits, approval and a test set.
- 17A helper that answers from your documentsAnswers with sources, scored on your own questions.
- 18A product that can chargeEmail from your own domain and a tested checkout, in test mode.
- 19A model tuned for one jobA small experiment, measured against your best prompt.
- 20A brand image kitOn-brand images from one saved workflow, with your own LoRA.
- 21A launch videoThirty to sixty seconds, with voice, music and sound.
- 22A tested, locked-down appEvery flow checked, and each person able to see only their own data.
- 23Your launched productThe finished product, in front of people, with a page that shows your work.
You start with
A connected assistant
Claude or ChatGPT connected to a tool you already use, with the right permissions.
Milestone 12Your product gains
Sign-in and saved data
That makes 13 of 23 pieces in place.
Your role
The steps change with your role. Choose yours to see your version of this milestone.
Start with this prompt
Paste it into Claude or ChatGPT, or into Claude Code once you are building. Fill in the parts in square brackets with your own product.
I am adding sign-in and a database to my app with Supabase. Here is what the app needs to remember: [list the things, such as projects, comments, invoices] Before changing anything, propose the tables: their columns, how they link to a user, and the row level security rule for each in plain words. Wait for me to agree. Then build sign-in first, and show me how to check that one account cannot see another account's data.
Build it step by step
7 steps, one from each lesson of the unit. Do each step after its lesson. A box you tick here is ticked in the lesson too.
Step 1 of 7 · from the lesson What a database is
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Design your tables on paper
Create a Supabase project. Then ask Claude to turn the Data section of your build brief into a list of tables and columns in plain words, and check it against the brief.
Done when
You will create the first table in the next lesson.
Step 2 of 7 · from the lesson Your first table
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Save your first real data
Have Claude Code create your first table and connect the app. Save one real item, refresh, and find the same row in the Supabase table editor.
Done when
Anyone can read this table for now. The next two lessons fix that.
Step 3 of 7 · from the lesson Login
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Add sign-in to your app
Have Claude Code add sign-up, sign-in, sign-out and protected pages with Supabase Auth. Test all four cases yourself with two different accounts.
Done when
Keep both accounts. You need them to test the next lesson.
Step 4 of 7 · from the lesson Row level security
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Lock down your data
Have Claude Code enable RLS on every table with rules from the Rules section of your brief. Then, with two accounts, try to read, change and delete the other account’s data.
Done when
Repeat this test whenever you add a table.
Step 5 of 7 · from the lesson File storage
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Add an upload
If your product needs files, have Claude Code add a private bucket with an upload, a size limit and signed links. Test that a second account cannot open the first account’s file. If it does not need files, note why in "My build".
Done when
You used the same pattern on this site for lesson films.
Step 6 of 7 · from the lesson Airtable as a quick backend
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Set up your back office in Airtable
Create a base for the data your team handles: at least a waitlist or leads table and one other table linked to it. Connect it to an n8n workflow so a new entry arrives automatically.
Done when
Keep customer data that must be private in Supabase.
Step 7 of 7 · from the lesson An admin panel in Retool
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepSign-in and saved data Build a small admin panel
In Retool, connect your database with a limited user and build one screen: search for a user, see their records, and perform one safe fix with a confirmation. Record every write in an audit table.
Done when
Write the support actions and who may do them into your README.
Publish it to GitHub
Your product repository
Commit the database migrations, or docs/schema.md with the tables and the access rule for each, and push. Keys stay out of the repository.
A milestone is not finished until it is pushed. A public repository with a history is how other people, including employers, can see what you built. Never commit a key, a token or anyone’s private data.
When it is done
Every box above is ticked, the work is pushed to GitHub, and you can show the result to someone who has not seen it before. Then move on: milestone 14 is your app, live.