From database-engineering
Design a correct relational schema: normalize to 3NF, denormalize only with measured evidence and a named consistency cost, push constraints (PK/FK/UNIQUE/CHECK/NOT NULL) into the database, and choose precise data types.
How this skill is triggered — by the user, by Claude, or both
Slash command
/database-engineering:relational-schema-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
3NF by default: each fact once, relationships via keys. Most 'we must denormalize' instincts are premature.
3NF by default: each fact once, relationships via keys. Most 'we must denormalize' instincts are premature.
Only with a measured read benefit AND the write/consistency cost named — often a materialized view or covering index is better than redundant columns.
PK on every table, FK for every relationship, NOT NULL/UNIQUE/CHECK to make illegal states unrepresentable. The app is not a trustworthy enforcer.
Precise numeric/temporal/text; uuid/enum/jsonb where they fit. text for everything + naive timestamps are smells.
npx claudepluginhub mcorbett51090/ravenclaude --plugin database-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.