supabase-to-insforge-skills

Use when migrating Supabase auth.users (and optionally auth.identities for OAuth) to modern InsForge auth.users + auth.user_providers. Preserves UUIDs (critical for FK integrity). Path A (direct Postgres, SUPABASE_DB_URL) copies bcrypt hashes so users keep passwords. Path B (no DB access — only a service_role / sb_secret_ key) exports users via the GoTrue Admin API and closes the password gap with a JIT bridge or reset.

Use when migrating PostgreSQL schema and data (including RLS policies, triggers, enum types, and functions) from a Supabase project to InsForge. Diagnoses target model first (modern auth.users vs legacy _accounts), applies minimal transforms, and loads via direct psql (bypassing InsForge's restrictive import API).

Use when rewriting a frontend codebase from @supabase/supabase-js to @insforge/sdk. Runs a grep-based inventory of call sites first, then rewrites imports, client init, auth flows, database queries, storage uploads, and function invocations. Flags patterns that don't auto-port (realtime channels, auth.admin session flows).

Use when a user wants to migrate an application from Supabase to InsForge. Orchestrates database, auth, storage, edge function, and frontend SDK migration. Runs a diagnostic probe first, produces an inventory report, selects strategy based on the target's actual schema shape, then dispatches to child skills in dependency order.

Use when migrating Supabase Edge Functions (Deno TS files) to modern InsForge Functions. Rewrites imports, handler shape, env vars, and SDK client init; deploys via raw HTTP API (stateless, automation-friendly). The DB row alone does not activate the runtime — deploy is mandatory.

Use when migrating Supabase Storage buckets and objects to modern InsForge storage. Creates buckets via SQL, downloads object bytes from source, uploads to target via HTTP API preserving exact keys, then runs a universal regex URL rewrite across all jsonb columns to fix embedded references.