Dang Supabase Mcp

Trigger

• The task requires schema, data, RLS, Edge Function, or advisor work through Supabase MCP tools.
• The change is production-impacting enough that preflight and QA order matter.
• A database fix needs explicit documentation of what changed and how it was verified.

Inputs

• Target database object or feature slice
• Required Supabase tool operations
• Relevant docs, parity IDs, and repro notes

Read First

1. sections/00-overview.md
2. sections/20-runbook.md
3. sections/30-failure-modes.md
4. sections/40-qa-checklist.md

Procedure

1. Load the overview and confirm the allowed change surface.
2. Follow the runbook in order instead of jumping straight to schema or data edits.