Stats
Actions
Tags
From role-database
Reviews and designs database schemas with normalization (1NF-BCNF), denormalization, multi-tenancy patterns, PK strategies (UUID v7, ULID, KSUID), soft deletes, temporal tables (SCD), audit trails, evolution, naming, data types, anti-patterns. For new schemas, reviews, migrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/role-database:schema-designThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load from `references/` based on what's needed:
Load from references/ based on what's needed:
Normal forms (1NF–4NF) with violation examples, denormalization patterns (materialized views, trigger counters). Multi-tenancy: shared schema + RLS, schema-per-tenant, database-per-tenant decision guide. Primary key strategy comparison (BIGSERIAL, UUID v7, ULID, Snowflake ID). Load when: designing new schemas, choosing PK strategy, implementing multi-tenancy.
Soft delete patterns (timestamp, archive table, partial indexes). SCD Type 2 temporal tables in PostgreSQL and SQL Server. Generic audit trigger with JSONB old/new values. Expand-contract pattern with safe migration operations table and zero-downtime column rename. Load when: implementing audit trails, versioned data, or zero-downtime schema changes.
Data type decisions (money, timestamps, IP, email, JSON, enums, country, phone). PostgreSQL domain types and range exclusion constraints. Naming conventions table (tables, columns, PKs, FKs, indexes, booleans, timestamps). Anti-patterns: EAV, polymorphic associations, god tables, over-indexing, missing FKs. Load when: choosing column types, reviewing naming, or identifying schema problems.
npx claudepluginhub rnavarych/alpha-engineer --plugin role-databaseDesigns normalized relational database schemas for PostgreSQL and MySQL from requirements, generating DDL, constraints, indexes, relationships, and migrations.
Designs PostgreSQL/MySQL schemas with normalization (1NF-3NF), relationships, constraints, audit columns. For new databases, reviews, migrations, or fixing missing PKs/FKs, wrong types, denormalization, EAV.
Designs and documents database schemas with entity relationships, table definitions, constraints, indexes, and access patterns. Useful when modeling entities or planning data models.