database-design

Automate database design guidance for schema patterns, migrations, and scaling.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/dinoudon/sdlc-skills --skill database-design-dinoudon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/dinoudon/sdlc-skills/tree/main/full/database-design
Command: npx skills add https://github.com/dinoudon/sdlc-skills --skill database-design-dinoudon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design decisions drive performance, maintainability, and scalability, yet teams often struggle to choose appropriate normalization levels, migration strategies, and indexing plans. This section explains how to design robust schemas, plan migrations, and optimize queries for evolving applications.

Core Features & Use Cases

  • Guidance on normalization (1NF–BCNF), schema patterns (star, snowflake), and when to denormalize for analytics.
  • Migration tooling and strategies (versioned migrations, zero-downtime approaches) to evolve schemas safely.
  • Indexing and query optimization patterns for OLTP/OLAP workloads, including JSONB, partitioning, and read replicas.
  • Real-world scenario: designing a multi-service order system with data-per-service boundaries and clear audit trails.

Quick Start

Define a baseline normalized schema for a multi-tenant e-commerce platform and generate an initial migration plan.

Frequently Asked Questions about database-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a database schema for a multi-tenant platform?

Database schema design for microservices requires establishing data-per-service boundaries with clear audit trails. It guides applying normalization, indexing, and migration tooling to ensure robust data modeling and performance tuning across independent services.

What's the best way to plan zero-downtime database migrations?

Zero-downtime database migrations are planned using versioned migration tooling and strategies that evolve schemas safely. This approach ensures continuous availability while applying normalization updates and indexing changes to OLTP workloads.

When should I denormalize a star schema for OLAP workloads?

Denormalization for OLAP workloads applies when transitioning from normalized schemas to star or snowflake schema patterns. This optimizes analytical query performance by structuring data specifically for read-heavy reporting instead of transactional integrity.

How do I optimize indexing for JSONB and partitioning in PostgreSQL?

Indexing for JSONB and partitioning is optimized by applying query performance tuning patterns tailored for OLTP and OLAP workloads. This includes structuring read replicas and leveraging JSONB indexing to accelerate complex document queries.

Does this database design approach work for both OLTP and OLAP systems?

This database design approach supports both OLTP and OLAP systems by enforcing tailored normalization levels, indexing plans, and schema patterns. It guides architecture planning to balance transactional throughput against analytical read performance.