What problem does it solve? It enforces a consistent, safe workflow for making Supabase backend changes in the Peajes / Transporte Ibarra project, preventing common mistakes like testing against the remote database, creating duplicate migration timestamps via MCP, or leaving the local CLI database without seed data. ## Core Features & Use Cases - Migration authoring and validation: Create SQL migrations for RPC functions, views, triggers, policies, and RLS, then validate them against the local Supabase CLI with pgTAP tests before any remote push. - Two-environment contract enforcement: Supabase CLI is the only testing environment and DESARROLLO is the only remote, with explicit guards against db reset --linked, MCP apply_migration duplicates, and hardcoded secrets. - Documentation and handoff: Every change is documented under docs/backend/ using the SQL task template, followed by the backend-documenter and backend-tester skills. - Use Case: When adding a new RPC for toll pass (pasadas) reporting, write the migration, run db reset --local --no-seed plus pgTAP tests, restore app data with pnpm seed:local, then push to DESARROLLO only after verifying migration history alignment. ## Quick Start Ask the agent to implement a new Supabase RPC or migration for the Peajes backend and validate it against the local Supabase CLI before pushing to DESARROLLO.