Plain words, and what to do when it's stuck.
Search for a word you don't know, or for what you're seeing on your screen.
Glossary
16- Repository (repo)
- The folder on GitHub that holds your dashboard's code and its history
- Commit
- A save point. You can always go back to one
- Push
- Sending your latest save points from your computer up to GitHub
- Deploy
- Vercel taking your code and putting it live at your link
- Deployment log
- Vercel's record of what happened during a deploy; where errors show up
- Localhost
- A preview that only exists on your own computer
- Environment variables
- Private settings (like your Supabase keys) kept outside the code
.env.local- The file on your computer that holds those settings
- Database
- Where your information is saved (Supabase)
- Table / row / column
- A spreadsheet tab / one item / one piece of information
- SQL
- The language used to set up database tables. Claude Code writes it; you paste and run it
- Row Level Security (RLS)
- The rule that you can only see your own rows
- Publishable key
- The Supabase key that's safe to use in your dashboard
- Secret key
- The Supabase master key. Never share or paste it
- Auth
- Login: who you are and what you're allowed to see
- Migration
- A SQL file that changes your database's structure
Troubleshooting
10- 01.
What you see
Things disappear after a refresh
Most likely cause
The data isn't saving to Supabase
What to do
Check the table exists in Table Editor; paste the browser error into Claude Code
- 02.
What you see
"Invalid API key" or nothing loads
Most likely cause
Keys are missing, swapped or mistyped
What to do
Re-copy the URL and publishable key into
.env.local(and Vercel), then restart the preview - 03.
What you see
Data saves but you can't see it
Most likely cause
Row Level Security policies are missing or wrong
What to do
Ask Claude Code to review the RLS policies for that table
- 04.
What you see
Login works on your computer, not on the live link
Most likely cause
Supabase URL Configuration still points to localhost
What to do
Repeat Step 7, Part C
- 05.
What you see
Magic link or confirmation email leads to an error page
Most likely cause
Redirect URL not added in Supabase
What to do
Add your live link with
/**to Redirect URLs - 06.
What you see
Vercel says the build failed
Most likely cause
A code error, or environment variables missing
What to do
Open the deployment log, copy the error, paste it into Claude Code
- 07.
What you see
Live site didn't change after an update
Most likely cause
The change wasn't pushed, or the deploy is still running
What to do
Ask Claude Code to push; check Vercel's Deployments tab
- 08.
What you see
Dashboard won't load after not using it for a while
Most likely cause
Free Supabase project paused
What to do
Sign in to Supabase and restore the project
- 09.
What you see
Claude Code changed things you didn't ask for
Most likely cause
The request was too broad
What to do
Use the Undo prompt, then ask for one change at a time
- 10.
What you see
You're stuck in a loop of fixes
Most likely cause
The conversation has gotten long and tangled
What to do
Start a fresh Claude Code conversation: "Read this project and summarize how it works," then describe the problem