Does it follow specific naming conventions?

Yes, it advocates for snake_case naming for tables and columns, pluralized table names, and standard audit columns like created_at and updated_at.

Does this skill replace Supabase client libraries?

No, it complements them by providing the architectural patterns and security rules that ensure the client libraries are used correctly and securely.

How does this skill help with Supabase security?

It enforces the use of Row-Level Security (RLS) policies and provides templates for common scenarios like user-owned data and friend-based access using the auth.uid() function.

Can I use this with .NET projects?

Yes, it includes specific patterns for C# Repository patterns, including mapping internal database entities to clean domain models using Supabase-specific attributes.

How are foreign keys handled?

The skill provides standard patterns for ON DELETE behavior, ensuring data integrity through CASCADE, SET NULL, or RESTRICT constraints depending on the relationship.

Supabase Patterns & Best Practices

Name: Supabase Patterns & Best Practices
Author: ReneBossen

byReneBossen

Database Management

Standardizes Supabase implementations by providing patterns for authentication, row-level security, and database schema design.

About

This skill equips Claude with specialized knowledge for architecting and implementing Supabase backends with a focus on security and scalability. It provides predefined patterns for Row-Level Security (RLS) policies, standardized SQL schema conventions, and seamless integration with C# repository patterns. It is particularly useful for developers building .NET or React Native applications who want to ensure their database architecture follows production-grade best practices while maintaining clean domain-entity separation and robust authorization logic.

Key Features

C# Entity-to-Domain mapping patterns for implementing the Repository design pattern.
0 GitHub stars
Automated database column standards for audit logging and foreign key constraint behaviors.
Best practices for Supabase Auth integration and JWT validation in backend middleware.
Standardized SQL schema conventions including snake_case naming and UUID primary keys.
Comprehensive Row-Level Security (RLS) templates for user-owned and shared data access.

Use Cases

Bootstrapping a secure multi-tenant database schema with robust RLS policies.
Implementing a clean C# backend architecture that interfaces with Supabase tables.
Standardizing database naming conventions and data types across a cross-platform project.

About

Key Features

C# Entity-to-Domain mapping patterns for implementing the Repository design pattern.
0 GitHub stars
Automated database column standards for audit logging and foreign key constraint behaviors.
Best practices for Supabase Auth integration and JWT validation in backend middleware.
Standardized SQL schema conventions including snake_case naming and UUID primary keys.
Comprehensive Row-Level Security (RLS) templates for user-owned and shared data access.

Use Cases

Bootstrapping a secure multi-tenant database schema with robust RLS policies.
Implementing a clean C# backend architecture that interfaces with Supabase tables.
Standardizing database naming conventions and data types across a cross-platform project.