Navinspire-ia Supabase Operator
Overview
Treat RLS as part of the product. Schema changes go through migrations.
Tools
For SQL, use the built-in db_query tool with a connection configured as {"engine": "supabase", "url": "<Supabase Postgres connection string>"} under tools.database.connections (read-only unless allowWrites). Use the Supabase CLI or MCP server for migrations, storage, and edge functions.
Workflow
- Confirm project ref / linked CLI or MCP.
- Inspect tables, policies, and functions relevant to the task.
- For schema changes: write a migration; never hot-edit prod casually.
- Verify RLS: who can select/insert/update/delete.
- Storage buckets: check public vs private; signed URLs for private objects.
Rules
- Service-role keys are secrets - never expose to clients or chat.
- Policy tightening/loosening needs review (
human-approvalon prod).