Glossary of Terms Every Vibe Coder Should Know

Introduction

Vibe coding tools (Lovable, V0, Bolt, etc.) often generate code with Supabase in the backend. Supabase is like the kitchen that serves your app's data (users, messages, orders, etc.). This glossary is your phrasebook for both general coding and Supabase-specific concepts.

Glossary

Basic Building Blocks

• Component — Reusable part of the UI (like a Lego block — button, navbar).
• Props — Inputs to a component (like a label for a button).
• State — The memory of a component (e.g., cart count in a shopping app).

Structure & Flow

• File Structure — How folders are organized (/components, /pages, /api).
• Routing — Decides what page to show for each URL.
• API — A bridge that lets your app fetch/send data (like asking a waiter for food).

Logic & Behavior

• Function — A small recipe step in code that performs one action.
• Event — Something triggered by the user (click, type, submit).
• Parameter — Extra details you give to a function (like spice level in food).

Styling & Design

• CSS — Rules that decide how the app looks (colors, fonts, layouts).
• Responsive Design — App adapts to desktop, tablet, and phone.
• Accessibility — Making the app usable for all (alt text, keyboard navigation).

Data & Storage (Supabase Core)

• Database — Where your data lives (Supabase uses PostgreSQL).
• Table — Like a spreadsheet where similar data is grouped (users, orders).
• Row / Record — A single entry in a table (one user, one order).
• Column — A field in the table (name, email, created_at).
• Query — Asking the database for specific data.
• RLS (Row Level Security) — Control who can access which rows (e.g., you can only see your own orders).
• Auth (Authentication) — Login/signup system to verify who you are.
• Storage — For handling files (images, PDFs, videos).

Supabase Advanced Features

• Edge Function — A serverless function deployed close to users (fast). Use cases: confirmation emails, custom API logic, payment verification.
• Realtime — Supabase can push live updates when data changes (like new chat messages appearing instantly).
• Policies — Rules that decide who can insert, read, update, delete data.
• Triggers — Automatic actions in the database when something happens (e.g., after a new order, create a log).
• Functions (DB) — SQL functions you define to automate complex queries.
• Webhooks — Notifications sent from Supabase to another service when something happens (e.g., notify Stripe after a payment).

Code Management

• Git — Tracks changes in your code.
• Repository (Repo) — A container for your project (on GitHub, GitLab, etc.).
• Commit — A saved version of your project.

Conclusion

You don't need to master PostgreSQL, RLS, or Edge Functions on day one. Just knowing the terms makes you confident to explore and fix things. The more you explore your vibe-coded project, the more natural these concepts will feel.