Database Design
A PostgreSQL schema guide that names the types you should never reach for.
Install
Claude Code: /plugin marketplace add wshobson/agents → /plugin install database-design@claude-code-workflows
PostgreSQL şeması tasarlanırken, tip ve indeks kararları verilirken ya da mevcut tablo yapısı gözden geçirilirken.
- Author
- Seth Hobson
- License
- MIT
Two agents and one skill, and the skill is unusually opinionated for reference material: it keeps an explicit do-not-use list where timestamp without a time zone, char and varchar with a length, and the money type each get a named replacement rather than a caveat. The gotchas section is the part worth keeping open while designing, because it collects behaviours that surprise people arriving from other engines. PostgreSQL does not index foreign key columns for you, a unique constraint accepts any number of nulls unless it is declared NULLS NOT DISTINCT, and identity sequences leave gaps after a rollback by design. Preferred defaults are stated plainly too, with bigint identity keys, numeric for money and timestamptz for event time.
Similar skills
PostgreSQL Optimization
SkillPostgreSQL-specific query, index and data-type guidance for a schema you already have.
AlloyDB for PostgreSQL Skills
SkillDrives an AlloyDB for PostgreSQL cluster from an agent: provisioning, schema, health and replication.
Supabase Agent Skills
SkillProduct guidance for Supabase plus a separate Postgres schema and performance skill.
Comments(0)
Sign in to comment