When does this skill recommend using Supabase RPC?

RPCs are recommended for operations involving three or more table joins, complex aggregations, or performance-sensitive batch processing to reduce client-side overhead.

What is the purpose of the SupabaseService base class?

It serves as the foundation for all domain-specific services, providing built-in utilities for error handling, logging, and privileged client access.

Why shouldn't I import the Supabase client directly in business logic?

Direct imports lead to fragmented database logic. This skill enforces a unified service layer to ensure consistent security, logging, and maintainability across the entire application.

How does this skill handle Service Role security?

Since the Service Role bypasses Row Level Security (RLS), this skill mandates explicit application-layer ID checks (e.g., .eq('user_id', userId)) to ensure data privacy.

Supabase Implementation Standards

Name: Supabase Implementation Standards
Author: shoma-endo

byshoma-endo

Gestión de Bases de Datos

Enforces standardized Supabase integration patterns using a unified service layer and secure Service Role management.

Acerca de

This skill establishes a Single Source of Truth (SSoT) for all Supabase operations within a project, ensuring consistent implementation through a centralized service architecture. It provides rigorous guidelines for subclassing the Supabase service, managing administrative privileges safely via the Service Role client, and implementing standardized error handling. By enforcing these patterns, it prevents fragmented database logic, enhances security through mandatory ownership checks even when RLS is bypassed, and optimizes performance by promoting Supabase RPCs for complex operations.

Características Principales

Unified service layer architecture via base class inheritance
Best practices for complex queries using Supabase RPC functions
Standardized error logging and user notification formatting
0 GitHub stars
Secure Service Role management with explicit bypass safety protocols
Centralized Supabase client instance management via dedicated manager

Casos de Uso

Building secure Next.js Server Actions with centralized database logic
Standardizing error handling and logging across large-scale Supabase applications
Managing background cron jobs or administrative tasks requiring privileged database access

Acerca de

Características Principales

Unified service layer architecture via base class inheritance
Best practices for complex queries using Supabase RPC functions
Standardized error logging and user notification formatting
0 GitHub stars
Secure Service Role management with explicit bypass safety protocols
Centralized Supabase client instance management via dedicated manager

Casos de Uso

Building secure Next.js Server Actions with centralized database logic
Standardizing error handling and logging across large-scale Supabase applications
Managing background cron jobs or administrative tasks requiring privileged database access