What this agent helps you do
A Neon Postgres and Supabase migration planning agent evaluates database changes across infrastructure and application services. Neon Postgres supplies project, branch, schema, and database context, while Supabase supplies backend, auth, policy, storage, and app-facing database context.
When to use this workflow
Use it for schema changes, migrations, backend refactors, branch previews, or app changes where database infrastructure and Supabase auth or policies both matter.
How Neon Postgres and Supabase give the agent context
Connect both plugins and define the migration, branch, or schema change. Neon should show database readiness; Supabase should show auth, RLS, and app-facing behavior. Any migration execution should require explicit human approval.
Example starter prompt
Review this Neon Postgres migration or branch, compare it with Supabase auth, RLS, and app-facing table impacts, and prepare a migration plan with preflight checks, rollback strategy, validation queries, and approval-required actions.Suggested workflow steps
Start with the schema change and affected application area. Have the agent inspect Neon branches and database assumptions, then review Supabase policies, auth flows, and tables that depend on the change.
Expected handoff
Ask for preflight checks, data risks, auth and RLS considerations, test queries, rollback strategy, owner recommendations, and explicit approval-required actions.