A comprehensive reference for PostgreSQL table design that covers the practical stuff you actually need: when to use BIGINT GENERATED ALWAYS AS IDENTITY versus UUID, why you should manually index foreign key columns, and how JSONB indexing works with GIN. It pushes you toward normalization first and includes the gotchas that bite people, like how PostgreSQL doesn't auto-index FKs and why UNIQUE constraints allow multiple NULLs. The guide is opinionated in useful ways, like preferring TEXT over VARCHAR and being explicit about avoiding certain types entirely. Good for both greenfield schema design and when you're refactoring existing tables and need to remember which index type actually makes sense for your query patterns.
npx skills add https://github.com/timescale/pg-aiguide --skill design-postgres-tables