supabase-bootstraplisted

# supabase-bootstrap ## Purpose Take an AiGNITE mobile project from "no backend" to "schema applied, RLS active, contract documented, table count verified" in one run. ## When to trigger Trigger on these user phrases. Match loosely. - "add a database" - "Supabase setup" - "auth setup" - "database for my app" - "set up Postgres" - "add user accounts" - "wire up Supabase" - "stand up the backend" ## Inputs to collect 1. Project name (defaults to the current folder name) 2. Hostinger VPS region nearest users (us-east, us-west, mumbai, frankfurt) 3. Table list with columns (the skill asks for these, or reads them from MVP_SPEC.md if present) 4. Authentication mode (email-password, magic-link, oauth) 5. Optional: 1Password vault name to store keys ## Behavior The skill runs nine steps in order. Each step must pass before the next runs. ### Step 1: Pre-flight - Confirm `supabase` CLI installed. If missing, abort with install instructions. - Confirm project root has `CLAUDE.md` and `.env.local.example`. If missing, suggest running `mobile-app-scaffold` first. ### Step 2: Initialize the project ``` supabase init supabase link --project-ref <ref> ``` If no project exists yet, `supabase projects create <name> --region <region>` runs first. ### Step 3: Generate the schema Read the table list. Render `supabase/migrations/0001_init.sql` from the schema template. Every table gets: - A UUID primary key - A `created_at timestamptz default now()` - A `user_id uuid references