Is this skill specific to Supabase?

While it is optimized for PostgreSQL 17 on the Supabase platform, the core principles of consistency and type safety are applicable to most modern PostgreSQL environments.

How does this skill handle naming conventions?

It enforces self-documenting names where the purpose and data type are indicated by naming patterns and suffixes, making the database easier to navigate for developers and AI.

What standard table structure does this skill promote?

It promotes using UUID primary keys with gen_random_uuid() and including timestamptz fields for created_at and updated_at as the default foundation for all tables.

What is the 'tight-fit' design philosophy?

Tight-fit design is the practice of only adding columns, indexes, or metadata fields when there is a confirmed requirement, preventing speculative database bloat and maintaining a lean schema.

Does this skill help with database migrations?

This skill focuses on the design principles; however, it is designed to work in tandem with the supabase-migration skill to ensure those designs are implemented correctly.

Supabase DB Conventions

Name: Supabase DB Conventions
Author: ninyawee

byninyawee

데이터베이스 관리

Standardizes PostgreSQL database design for Supabase projects using tight-fit principles and consistent naming patterns.

소개

This skill provides Claude with specialized architectural guidance for designing and maintaining PostgreSQL 17 databases within the Supabase ecosystem. It enforces a 'tight-fit' design philosophy, preventing the premature addition of speculative columns like soft deletes, audit trails, or metadata fields until they are explicitly required by the project. By implementing standardized table structures, predictable naming conventions, and type-safety patterns, this skill ensures your database remains lean, self-documenting, and optimized for high-performance Supabase applications.

주요 기능

0 GitHub stars
Enforces 'tight-fit' design to prevent speculative database schema bloat
Standardizes PostgreSQL 17 naming conventions and type-safety suffixes
Ensures database objects follow predictable, self-documenting patterns
Integrates with related Supabase workflows for migrations and seeding
Provides boilerplate for standard table structures including UUIDs and timestamps

사용 사례

Refactoring existing tables to follow consistent PostgreSQL naming patterns
Applying the tight-fit philosophy to minimize database complexity and technical debt
Designing a new Supabase database schema from scratch using best practices

소개

주요 기능

0 GitHub stars
Enforces 'tight-fit' design to prevent speculative database schema bloat
Standardizes PostgreSQL 17 naming conventions and type-safety suffixes
Ensures database objects follow predictable, self-documenting patterns
Integrates with related Supabase workflows for migrations and seeding
Provides boilerplate for standard table structures including UUIDs and timestamps

사용 사례

Refactoring existing tables to follow consistent PostgreSQL naming patterns
Applying the tight-fit philosophy to minimize database complexity and technical debt
Designing a new Supabase database schema from scratch using best practices