What this agent helps you do
A Supabase and Vercel backend preview debugging agent diagnoses preview issues involving data, auth, policies, or deployment configuration. Supabase supplies database, auth, RLS, storage, and backend context, while Vercel supplies deployment, preview, build, environment, and runtime context.
When to use this workflow
Use it for failing preview URLs, staging regressions, auth issues, data bugs, environment mismatches, or feature previews that work locally but not in deployed previews.
How Supabase and Vercel give the agent context
Connect both plugins and provide the failing preview URL, deployment, or feature area. Vercel should show how the app deployed; Supabase should show whether the backend is ready for that environment. Any production configuration change should require approval.
Example starter prompt
Review this Vercel preview deployment and Supabase backend context. Identify likely root causes, environment mismatches, policy concerns, database checks, and approval-ready fixes for the failing feature.Suggested workflow steps
Start with the deployment URL and failing flow. Have the agent inspect Vercel build status, logs, environment variables, and routes, then compare them with Supabase tables, auth settings, RLS policies, and backend configuration.
Expected handoff
Ask for likely root causes, environment mismatches, policy concerns, database checks, validation steps, release risks, and approval-ready fixes.