Supabase Cli

Operating Rules

• Prefer local validation before remote changes:
  • local schema change -> db reset / db lint
  • function change -> functions serve
• Before remote ops, identify exact target:
  • supabase projects list
  • confirm project-ref
  • confirm linked state
• Before db push, inspect pending migrations; use dry run/help if available on installed CLI.
• Before destructive local ops (db reset, stop --no-backup), warn about data loss; back up if needed.
• For existing hosted projects, pull remote schema before creating new local migrations.
• After schema changes, refresh checked-in generated types if repo uses them.
• Quote exact CLI errors when debugging.

Defaults

• Use npx supabase ... in Node repos unless the repo already standardizes on global supabase.
• Use supabase init + supabase start for new local environments.
• Use supabase login + supabase link --project-ref ... before hosted-project operations that need linking.
• Use migrations as source of truth; avoid dashboard-only schema edits unless intentionally pulling them back into code.
• Use --no-verify-jwt only for intentionally public/webhook Edge Functions.

Output

• Report:
  • command path used (npx supabase vs global)
  • linked project/environment
  • files touched under supabase/
  • exact verification run
  • exact error text if blocked