From role-database
Database schema design principles and patterns. Normalization (1NF through 5NF/BCNF), strategic denormalization for read performance, multi-tenancy schema patterns (shared schema, schema-per-tenant, database-per-tenant), primary key strategies (UUID v7, ULID, KSUID, Snowflake ID, BIGSERIAL, CUID2, NanoID), soft delete patterns, temporal tables (SCD Type 1/2/3/4/6), audit trails, schema evolution (expand-contract pattern), naming conventions, data type best practices, and anti-patterns to avoid (EAV, polymorphic associations, god tables). Use when designing new schemas, reviewing existing schema design, planning schema migrations, or choosing PK strategies.
npx claudepluginhub rnavarych/alpha-engineer --plugin role-databaseThis skill is limited to using the following tools:
Load from `references/` based on what's needed:
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
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.