Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
davila7 avatar

Database Design

  • 527 installs
  • 30.1k repo stars
  • Updated August 4, 2026
  • davila7/claude-code-templates

database-design is a Claude Code skill that generates production-ready database schemas, relationships, indexes, and migration plans from natural language requirements for developers who need structured SQL or NoSQL data

About

database-design is a Claude Code skill from davila7/claude-code-templates that turns natural language product requirements into production-oriented database artifacts. The skill produces entity-relationship structures, foreign-key relationships, index recommendations, and step-by-step migration plans suitable for PostgreSQL, MySQL, and similar relational stacks. Developers reach for database-design when bootstrapping a new service, refactoring a monolith schema, or translating PRD tables and workflows into normalized tables before writing ORM models or raw SQL migrations. With 508 installs on skills.sh, it fits early backend sprints where schema mistakes are expensive to unwind later.

  • Converts product requirements into normalized relational or NoSQL schemas
  • Outputs complete DDL, migration files, seed data, and query examples
  • Includes indexing strategy, constraints, and performance recommendations
  • Produces entity-relationship diagrams in Mermaid format
  • Delivers ready-to-apply artifacts that feed directly into your ORM or query layer

Database Design by the numbers

  • 527 all-time installs (skills.sh)
  • Ranked #119 of 911 Databases skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill database-design

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs527
repo stars30.1k
Last updatedAugust 4, 2026
Repositorydavila7/claude-code-templates

How do you design a production database schema from requirements?

Generate production-ready database schemas, relationships, indexes, and migration plans from natural language requirements.

Who is it for?

Backend engineers starting a new feature or service who need normalized schemas and migration steps before writing ORM code.

Skip if: Teams that already have finalized schemas and only need query tuning or DBA-level performance audits.

When should I use this skill?

A developer describes data entities, relationships, or storage needs and asks for schema, ERD, or migration output.

What you get

Entity-relationship schema, relationship map, index recommendations, and migration plan documents.

  • ER schema
  • migration plan
  • index recommendations

By the numbers

  • 508 installs on skills.sh
  • Generates schemas, relationships, indexes, and migration plans as bundled outputs

Files

SKILL.mdMarkdownGitHub ↗

Database Design

Learn to THINK, not copy SQL patterns.

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.

FileDescriptionWhen to Read
database-selection.mdPostgreSQL vs Neon vs Turso vs SQLiteChoosing database
orm-selection.mdDrizzle vs Prisma vs KyselyChoosing ORM
schema-design.mdNormalization, PKs, relationshipsDesigning schema
indexing.mdIndex types, composite indexesPerformance tuning
optimization.mdN+1, EXPLAIN ANALYZEQuery optimization
migrations.mdSafe migrations, serverless DBsSchema changes

---

⚠️ Core Principle

  • ASK user for database preferences when unclear
  • Choose database/ORM based on CONTEXT
  • Don't default to PostgreSQL for everything

---

Decision Checklist

Before designing schema:

  • [ ] Asked user about database preference?
  • [ ] Chosen database for THIS context?
  • [ ] Considered deployment environment?
  • [ ] Planned index strategy?
  • [ ] Defined relationship types?

---

Anti-Patterns

❌ Default to PostgreSQL for simple apps (SQLite may suffice) ❌ Skip indexing ❌ Use SELECT * in production ❌ Store JSON when structured data is better ❌ Ignore N+1 queries

Related skills

Forks & variants (1)

Database Design has 1 known copy in the catalog totaling 3 installs. They canonicalize to this original listing.

How it compares

Choose database-design when requirements exist but no schema yet; use query-optimization skills after tables are live.

FAQ

What does database-design output?

database-design outputs production-ready database schemas with entity relationships, recommended indexes, and a migration plan derived from natural language requirements, giving developers artifacts ready for ORM models or SQL migration files.

When should developers use database-design?

Developers should use database-design at the start of a backend build when tables, keys, and migrations are undefined. The skill converts feature requirements into normalized schemas before application code is written.

Databasesbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.