How does the skill handle primary keys?

It recommends a standard structure using UUIDs as primary keys, utilizing the gen_random_uuid() function for secure and scalable identification.

Can this skill help with database migrations?

While this skill focuses on design principles, it is designed to work alongside the 'supabase-migration' skill to handle the actual creation and naming of migration files.

Does this skill follow a specific SQL standard?

Yes, it is optimized for PostgreSQL 17 conventions specifically as implemented on the Supabase platform.

What is the 'tight-fit' design philosophy used in this skill?

The tight-fit philosophy dictates that developers should only add columns and indexes when there is a confirmed requirement, avoiding speculative fields like 'deleted_at' or 'metadata' until they are actually needed.

Why does it emphasize type-safe naming?

Type-safe naming through suffixes allows developers and AI agents to understand the underlying data structure of a table or column immediately without checking the schema definition.

Supabase Database Design

Name: Supabase Database Design
Author: ninyawee

byninyawee

データベース管理

Enforces lean PostgreSQL conventions and a tight-fit design philosophy for optimized Supabase database schemas.

概要

This skill equips Claude with expert-level guidance for architecting PostgreSQL 17 databases within the Supabase ecosystem, focusing on a 'tight-fit' design philosophy that eliminates speculative schema bloat. By implementing strict naming conventions, type-safe suffixes, and standardized table structures, it ensures that your database remains lean, self-documenting, and highly performant. It is particularly useful during the initial design phase of a project or when refactoring existing schemas to align with professional database engineering standards.

主な機能

Implements a 'tight-fit' design philosophy to prevent speculative column additions
Provides specific architectural guidance for PostgreSQL 17 on Supabase
Standardizes table structures using UUID primary keys and timestamptz fields
Enforces consistent, self-documenting naming patterns for all database objects
Ensures type safety through standardized naming and suffix conventions
0 GitHub stars

ユースケース

Architecting initial database schemas for new Supabase applications
Refactoring legacy table structures to meet modern PostgreSQL standards
Enforcing consistent naming and design patterns across large development teams

概要

主な機能

Implements a 'tight-fit' design philosophy to prevent speculative column additions
Provides specific architectural guidance for PostgreSQL 17 on Supabase
Standardizes table structures using UUID primary keys and timestamptz fields
Enforces consistent, self-documenting naming patterns for all database objects
Ensures type safety through standardized naming and suffix conventions
0 GitHub stars

ユースケース

Architecting initial database schemas for new Supabase applications
Refactoring legacy table structures to meet modern PostgreSQL standards
Enforcing consistent naming and design patterns across large development teams