How conversion works
Creating a Vibe project against an existing app pulls that app's full schema — tables, fields, connections, roles, workflows, and per-table RLS scope — into tada/schema.json, then runs a one-time, deterministic scaffolder that writes the starting screens. After that first pass, the agent owns the files and you refine by chatting.
Choose how it starts
| Start mode | What you get |
|---|---|
| Start from data (default) | A clean list / detail / form set for each user-facing table, plus a dashboard. |
| Mirror my app | Screens modeled on your existing Layouts and Pages, as a closer starting point. |
| Let AI design it | An AI design pass that composes a tailored UI. Rolling out — may not be available on your account yet. |
What the app needs first
- Real data tables beyond Users — an app with only a Users table is rejected as "nothing to build."
- RLS enabled for API access, so Vibe can read data as the signed-in user (see the next article).
- Roles configured, if different users should see different things.