Skip to content
Kitbay
Skill

supabase-production

MITUpdated on Nov 14, 2026586GitHub stars

A skill from Pawel Huryn's product engineering set with opinionated rules for running Supabase in production, written for a Next.js, Clerk and Netlify stack.

What the skill teaches

A skill from Pawel Huryn's product engineering set with opinionated rules for running Supabase in production, written for a Next.js, Clerk and Netlify stack. Only the app server holds the key that bypasses row level security; other runtimes get narrow roles. Tables use row level security with no policies, so all direct access is denied and authorisation lives in tested code, with public grants revoked. Schema changes are numbered migration files applied by the Supabase CLI to an explicitly named database URL, never through the dashboard, a linked project or the MCP server, which is kept for read-only checks. Production migrations need the owner's approval, a dry run and a ledger check before and after.

Capabilities

  • Set deny-all row level security and revoke grants
  • Apply migrations with the CLI to a named target
  • Check the migration ledger before a release
  • Keep separate development and production projects