Schema
The blueprint of how your database is organized.
What is Schema?
A schema defines what tables exist in your database and what columns each table has. Like deciding a spreadsheet will have columns for Name, Email, and Date before you start filling it in.
Getting your schema right early saves a lot of headaches. If you forget a column, you'll need a migration to add it later — which is doable but adds complexity.
In Vibe Coding
When you tell Lovable "I need a blog with posts and comments," it creates a schema — a users table, a posts table, and a comments table with the right columns. In Cursor, you can view your schema in Supabase's dashboard.
Example
For example: Your schema for a simple store might have three tables: products (name, price, image), orders (user, date, total), and customers (name, email, address).
Why this matters
This matters because Schema appears repeatedly when building, deploying, debugging, or connecting services in vibe coding workflows.
When you'll hit this in practice
You will usually run into Schema when working on Pick Your Stack.