What problem does it solve? Teams running Neon Postgres with Drizzle ORM on SvelteKit and Vercel repeatedly hit the same mistakes: wrong driver for the runtime, pooled connections used for migrations, unsafe drizzle-kit push against production data, and incomplete Supabase migrations that silently break user foreign keys. This Skill encodes cited, decision-tree-driven guidance so those choices are made correctly the first time. ## Core Features & Use Cases - Connection and driver decisions: Choose pooled vs direct connections and the right driver (pg with attachDatabasePool on Vercel Fluid, @neondatabase/serverless on Edge) per route, with a printable decision matrix. - Schema, migrations, and branching: Design Drizzle schemas with relations and indexes, run generate/migrate workflows safely, and wire Neon's branch-per-PR GitHub Actions flow with schema-diff PR comments. - Supabase migration: Execute pg_dump/pg_restore cutovers, remap user IDs after switching auth to WorkOS, translate RLS policies, and plan replacements for Storage and Realtime, which have no Neon-native equivalent. - Use Case: Migrating a Supabase-backed SvelteKit app to Neon: the Skill walks you through dumping the database, rewriting auth.uid() policies to auth.user_id(), remapping every user_id foreign key via an email mapping table, and flagging that Storage and Realtime need separate replacements. ## Quick Start Ask the agent to review your Drizzle schema and drizzle.config.ts and recommend the correct Neon connection pattern and migration workflow for your SvelteKit app on Vercel.