Database schema design for PostgreSQL/MySQL with normalization, relationships, constraints. Use for new databases, schema reviews, migrations, or encountering missing PKs/FKs, wrong data types, premature denormalization, EAV anti-pattern.
94
92%
Does it follow best practices?
Impact
98%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Primary keys, foreign keys, indexes, and audit columns
UUID primary keys
0%
100%
All tables have PKs
100%
100%
Foreign keys explicit
100%
100%
ON DELETE/UPDATE specified
100%
100%
FK indexes present
100%
100%
Audit columns all tables
50%
100%
TIMESTAMPTZ for timestamps
100%
100%
NOT NULL on required fields
100%
100%
Bounded VARCHAR lengths
100%
100%
DECIMAL for money
100%
100%
CHECK for enum status
100%
100%
CHECK for numeric ranges
100%
100%
Normalization, EAV avoidance, naming conventions, soft deletes
No EAV pattern
100%
100%
JSONB for metadata
100%
70%
GIN index on JSONB
100%
100%
Soft delete pattern
100%
100%
Junction table for M:M
100%
100%
Table naming convention
100%
100%
FK column naming
100%
100%
Index naming convention
100%
100%
Normalized 3NF
100%
100%
NOT NULL required fields
100%
100%
Bounded VARCHAR
100%
100%
TIMESTAMPTZ audit columns
75%
75%
No polymorphic comments
100%
100%
Cascade rules, updated_at triggers, BOOLEAN types, data types
CASCADE on org delete
100%
100%
CASCADE on project delete
100%
100%
SET NULL on user delete
100%
100%
updated_at trigger function
100%
100%
Trigger on each table
100%
100%
BOOLEAN for flags
100%
100%
CHECK on status enum
70%
100%
CHECK on priority range
100%
100%
UUID primary keys
0%
100%
FK indexes present
100%
100%
TIMESTAMPTZ audit columns
100%
100%
NOT NULL on required fields
100%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.