db-design

Design relational database schemas with 3NF normalization, constraints, and index strategies.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chicongst/agent-skills-installer --skill db-design-chicongst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-design
Source: https://github.com/chicongst/agent-skills-installer/tree/main/skills/db-design
Command: npx skills add https://github.com/chicongst/agent-skills-installer --skill db-design-chicongst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing databases can be error-prone and slow without a rigorous approach to data modeling, constraints, and migrations. This skill produces robust, scalable schemas that prevent anomalies and support evolving requirements.

Core Features & Use Cases

  • 3NF-first data modeling with sensible denormalization where justified
  • Enforces constraints at the database level (NOT NULL, UNIQUE, FOREIGN KEY)
  • Thoughtful indexing and migration planning for zero-downtime evolution

Quick Start

Provide a first-pass database design for a given domain by outlining entities, relationships, and constraints.

Frequently Asked Questions about db-design

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

FAQPage Schema
How do I design a database schema that enforces constraints and supports efficient queries?

Database schema design for OLTP systems requires 3NF normalization to eliminate anomalies, enforcing constraints like NOT NULL, UNIQUE, and FOREIGN KEY at the database level, with sensible denormalization applied only where justified for performance.

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

Planning zero-downtime database migrations involves building reversible steps that evolve schemas without disrupting active queries, ensuring constraint integrity and preventing data anomalies during deployment.

How do I build an index strategy aligned to query patterns for an OLTP system?

Building an index strategy aligned to query patterns requires analyzing OLTP access paths to create performance-aware indexes that accelerate frequent lookups without degrading write throughput.

When do I need 3NF normalization for relational data modeling?

You need 3NF normalization for relational data modeling when your application requires strict data integrity and anomaly prevention, applying sensible denormalization only when specific query performance needs justify it.

Does this database design approach work for high-scale OLTP systems?

This database design approach works for OLTP systems by producing robust, scalable schemas that enforce constraints and support efficient queries, tailored for transactional workloads requiring zero-downtime evolution.