supabase-mastery

Enforce migration-based Supabase schema changes with RLS and auditing.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lshtram/core_dev --skill supabase-mastery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-mastery
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/supabase-mastery
Command: npx skills add https://github.com/lshtram/core_dev --skill supabase-mastery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supabase-mastery ensures every database change is secure, traceable, and migration-based, preventing silent schema drift and unreviewed deployments.

Core Features & Use Cases

  • Enforce migration-based changes with mandatory RLS and auditing.
  • Provide a standardized change proposal and review workflow for database changes.
  • Use Case: When updating a table schema in a Supabase project, generate a migration proposal, review it, and apply after approval.

Quick Start

Draft and review a migration for the next Supabase schema change before applying it.

Frequently Asked Questions about supabase-mastery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce migration-based deployments for Supabase database changes?

Migration-based deployments for Supabase are enforced by applying all schema changes through controlled SQL drafts, mandating RLS enforcement, and running post-change security checks. This prevents silent schema drift and unreviewed updates.

What is the best way to secure Supabase schema updates with RLS and auditing?

Securing Supabase schema updates requires mandatory Row Level Security (RLS) enforcement and ongoing auditing applied to every migration. Draft SQL in a controlled manner, require user review, and execute security checks after each change.

How do I generate a migration proposal for a Supabase table schema update?

Generating a migration proposal for a Supabase table schema update involves drafting the SQL changes in a controlled manner within a standardized review workflow. The system requires user review and approval before applying the schema migration.

Why do I need mandatory RLS enforcement for Supabase database migrations?

Mandatory RLS enforcement for Supabase database migrations is needed to secure every database change against unauthorized access. It ensures traceable, migration-based deployments while preventing silent schema drift and unreviewed security vulnerabilities.

Does Supabase support a standardized change proposal and review workflow for database migrations?

Supabase supports a standardized change proposal and review workflow by drafting SQL in a controlled manner, requiring explicit user review before applying migrations, and running automated security checks after each schema modification.