supabase-auth-rls

Scaffold a Supabase project with authentication and Row Level Security policies.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/jamescha-earley/agent-skills --skill supabase-auth-rls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-auth-rls
Source: https://github.com/jamescha-earley/agent-skills/tree/main/supabase-auth-rls
Command: npx skills add https://github.com/jamescha-earley/agent-skills --skill supabase-auth-rls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Supabase projects often suffer from misconfigured Row Level Security (RLS) and incomplete auth integration, which can expose data or block legitimate users. This skill guides you through scaffolding a local Supabase project with a properly designed database schema, RLS policies, and authentication hooks to enforce safe, multi-tenant access.

Core Features & Use Cases

  • Step-by-step workflow from requirements gathering to generating a typed client, including local development setup with Supabase CLI, schema design with auth.users integration, and creation of RLS policies.
  • Reference-guided approach using bundled templates and guides to configure projects, policies, and verification without building boilerplate from scratch.
  • Supports multi-tenant patterns (organizations/members) with role-based access, profile triggers, and policy verification.

Quick Start

Outline your app's access patterns and run the local Supabase workflow to initialize and start the project.

Frequently Asked Questions about supabase-auth-rls

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

FAQPage Schema
How do I set up Row Level Security policies in Supabase to prevent data leakage?

You can configure Supabase RLS by enabling RLS on tables, integrating the schema with auth.users, and creating specific policies to enforce safe multi-tenant access, which prevents data leakage from misconfigurations.

What is the best way to structure a multi-tenant Supabase database with auth and RLS?

Structuring a multi-tenant Supabase database involves using organizations and members patterns with role-based access, creating profile triggers, and applying RLS policies to isolate tenant data securely.

How do I add RLS policies to existing tables in a Supabase project?

You add RLS policies to existing Supabase tables by generating migration templates that enable RLS and define access rules based on your current auth integration, securing data without rebuilding schemas.

Do I need the Supabase CLI to scaffold local authentication and RLS workflows?

Yes, using the Supabase CLI for local development setup scaffolds projects with proper authentication and RLS, supporting initialization, schema design, and migration template generation.

Why does my Supabase auth integration block legitimate users when RLS is enabled?

Supabase auth integration blocks legitimate users when RLS policies are incomplete or misconfigured. Fixing this requires reviewing policy creation logic, verifying org membership patterns, and correcting role-based access rules.