Scene picks
Postgres schema, then queries
Normalize first, then Postgres-specific types and indexes. Supabase notes only if you host there.

Why these
database-design is generic. postgresql-table-design is the one that will argue with you about types and indexes. Read them in that order or you will denormalize before you have a normal form to denormalize.
Install in this order
First. Keys, normalization, and the migration sequence. The examples are Postgres-flavored, but the decisions are the model.
Second, once the entities exist. Types, constraints, and indexes for Postgres specifically.
Only on Supabase. Skip it on RDS or a local Postgres. The advice assumes that platform.
After the tables exist. Wide events, so a slow query has a line you can find. Not a schema tool.
Not for this
Picking Nest or FastAPI. Use the API pick after this one. I did not execute the SQL from database-design on 2026-11-04: nothing was listening on the local Postgres socket.