supabase

Manage Supabase schema changes, RLS policies, Edge Functions, and storage via CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Maykesantos98/Fiap-Totvs --skill supabase-maykesantos98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/Maykesantos98/Fiap-Totvs/tree/main/.claude/skills/supabase
Command: npx skills add https://github.com/Maykesantos98/Fiap-Totvs --skill supabase-maykesantos98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction and risk of managing a Supabase project’s database schema, auth, RLS, and serverless functions by providing a consistent local-first workflow that keeps production changes controlled and reviewable.

Core Features & Use Cases

  • Local-first Supabase CLI workflow: initialize projects, link to a remote project, start/stop the local stack, and pull existing schema to keep environments aligned.
  • Migration-driven database evolution: generate diffs or create migrations directly, review SQL before applying, and push migration history to staging/production.
  • Security patterns (RLS + auth linkage): enable RLS, define least-privilege policies, and structure tables that reference auth.users for owner-only access.
  • Edge Functions + Storage basics: scaffold and deploy Deno-based functions with auth context, and set up storage buckets/policies for safe file access.

Use case: A team needs to add a new table and ensure only authenticated users can read/update their own records—use migrations plus RLS policies to implement the change locally, review the generated SQL, then push it to the remote environment.

Quick Start

Use the supabase CLI to start your local stack, create or edit migrations for your schema change, then run a database reset locally and push the migrations to your Supabase project.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I manage Supabase database migrations locally before pushing to production?

Supabase migrations are managed locally by initializing the local stack with the CLI, creating or diffing SQL migration files, reviewing the generated schema changes, and then pushing the migration history to the remote production environment.

How do I set up Row Level Security policies for Supabase tables linked to auth users?

Row Level Security policies are set up by enabling RLS on the target table and defining least-privilege policies that reference the auth.users table, ensuring only authenticated users can read or update their own records.

What is the best way to deploy Supabase Edge Functions with auth context?

Deploying Supabase Edge Functions involves scaffolding Deno-based functions locally, configuring the necessary auth context within the code, and using the CLI to push the functions to your remote Supabase project.

Can I configure Supabase storage buckets and file access policies using the CLI?

Yes, Supabase storage buckets and file access policies can be configured using the CLI workflow, allowing you to define bucket structures and security rules locally before applying them to the remote environment.

Do I need the Supabase CLI to link my local development environment to a remote project?

Yes, the Supabase CLI is required to link your local development environment to a remote project, which keeps your local database schema, auth, and serverless functions aligned with the production setup.

Why should I review generated SQL before applying a database reset locally in Supabase?

Reviewing generated SQL before applying a database reset locally ensures that schema changes and RLS policies are safe and correct, preventing unintended data loss or security misconfigurations before pushing to staging or production.