database-schema-designer

Design normalized SQL and NoSQL database schemas with indexes, constraints, and reversible migrations.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill database-schema-designer-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-schema-designer
Source: https://github.com/Tgoldi/claude-skills/tree/main/database-schema-designer
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill database-schema-designer-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Designing a database schema from scratch involves many decisions—normalization levels, data types, indexing, foreign key strategies, and migration safety—that are easy to get wrong and costly to fix later. This Skill guides the full schema design process so the resulting data model maintains integrity and query performance. ## Core Features & Use Cases - Schema Generation: Produces complete SQL table definitions with primary keys, foreign keys, constraints, and indexes from a plain-language description of entities and relationships. - Normalization & Optimization Guidance: Applies 1NF through 3NF rules, advises when denormalization is justified, and plans composite index strategies based on access patterns. - Migration Planning: Generates reversible up/down migration scripts with zero-downtime patterns like nullable-column-first rollouts. - Use Case: Describe an e-commerce platform with users, products, and orders, and receive a complete SQL schema with indexed foreign keys, DECIMAL money columns, and timestamps, plus a checklist to verify the design. ## Quick Start Ask the assistant to design a schema for your application domain, listing the main entities, their relationships, and whether the workload is read-heavy or write-heavy.

Frequently Asked Questions about database-schema-designer

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

FAQPage Schema
How do I design a database schema for a new application?

Start by listing your entities, relationships, and access patterns, then normalize to 3NF before adding constraints and indexes. This Skill generates complete CREATE TABLE statements with primary keys, foreign keys, and appropriate data types from that description.

Should I use SQL or NoSQL for my data model?

The choice depends on access patterns: SQL suits relational data with joins and transactions, while NoSQL like MongoDB fits document-oriented data read together. The Skill defaults to SQL but covers MongoDB embedding versus referencing trade-offs.

How do I add a column to a production table without downtime?

Add the column as nullable first, deploy code that writes to it, backfill existing rows, then add the NOT NULL constraint. This multi-step pattern keeps the migration backward compatible and reversible.

Why should I avoid FLOAT for storing money in a database?

FLOAT uses approximate arithmetic, causing rounding errors on monetary values. Use DECIMAL(10,2) instead, which stores exact precision suitable for financial calculations.

When should I denormalize a database schema?

Denormalize only for read-heavy workloads where expensive JOINs or aggregations hurt performance, such as reporting dashboards. Document the reason and consider materialized views or pre-calculated columns instead of duplicating source data.