supabase-integration

name	supabase-integration
description	Wire a Supabase backend into a freshly created app the right way the first time — schema, RLS, auth, migrations, and type-safe client — driven by the Supabase MCP. Use when the /design app-creation flow (or any task) needs to give a new app a working, secure Postgres backend. Triggers: 'add a backend', 'store data', 'save submissions', 'log in', 'user accounts', 'database', Supabase, RLS, migrations, auth, edge functions. Respond to designers/PMs in plain language; do the engineering underneath.
metadata	{"author":"[e-mail]","version":"0.1.0","date":"2026-06-12T00:00:00.000Z","builds-on":"supabase/agent-skills (supabase, supabase-postgres-best-practices)"}

Supabase Integration (best-practice backend for new apps)

This skill gives a newly created app (from /design) a backend that is secure and correct on the first try, so it actually runs. It is the engineer's half of the designer/PM workflow:

Think as a database engineer. Respond as a designer/PM. Never show raw SQL or migration files unless asked. Translate "save the brief" → a table + RLS + a typed client call, and report back in plain language ("Briefs are now saved per user; nobody can see anyone else's.").

It builds on the official Supabase skills (supabase, supabase-postgres-best-practices), which now ship bundled with this plugin — no separate install. Defer to them for deep Postgres performance rules and current Supabase API details; this skill is the opinionated app-creation path on top.

---

0. Verify before you build (do not trust training data)

Supabase changes often. Before writing schema or auth code: