Explain PostgreSQL database design conventions for Supabase projects.
npx skills add https://github.com/ninyawee/dotfiles --skill supabase-db
Please help me install this Agent Skill. Skill: supabase-db Source: https://github.com/ninyawee/dotfiles/tree/main/dot_claude/saved_skills/supabase-db Command: npx skills add https://github.com/ninyawee/dotfiles --skill supabase-db
This Skill provides a clear overview of PostgreSQL conventions specifically tailored for Supabase projects, helping developers maintain consistency and understand best practices for database design.
id, created_at, and updated_at.Provide an overview of PostgreSQL conventions for Supabase projects.
High-intent search queries and answers about installing and using this skill.
Standard PostgreSQL conventions for Supabase focus on consistency, self-documenting names, and type safety to ensure maintainable schemas. They provide a clear template for creating tables with essential fields like id, created_at, and updated_at.
To structure a new table schema in Supabase, follow a tight-fit design philosophy using a standard template. Include essential fields like id, created_at, and updated_at, and only add specific columns like deleted_at or metadata when explicitly needed.
You should add metadata or deleted_at columns to a PostgreSQL table only when needed, adhering to a tight-fit design philosophy. This approach avoids speculative column additions, keeping the database schema efficient and maintainable.
Tight-fit design philosophy in PostgreSQL schema creation dictates when to add columns and when to avoid speculative additions. It ensures database design remains efficient by preventing unnecessary fields from cluttering the table structure.
Supabase PostgreSQL conventions emphasize consistency and self-documenting names for database schemas. This naming approach ensures that the database structure remains maintainable and easily understood by new developers joining the project.
Yes, these PostgreSQL conventions maintain type safety in Supabase projects by establishing standard table structures. They help developers understand established database schema conventions and add new tables following best practices for consistency.
FindMalekConfigure Prisma for multiple database providers and set up the client.
tagtyCreate, edit, and apply SQL migrations to a Supabase PostgreSQL database.
SaschaLehDesign and enforce Supabase Row Level Security policies for PostgreSQL tables.
ChatAndBuildDesign PostgreSQL database tables with primary keys, column types, normalization, and indexing.