Database Design

1---2name: database-design3description: "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."4risk: safe5source: community6date_added: "2026-02-27"7---8 9# Database Design10 11> **Learn to THINK, not copy SQL patterns.**12 13## 🎯 Selective Reading Rule14 15**Read ONLY files relevant to the request!** Check the content map, find what you need.16 17| File | Description | When to Read |18|------|-------------|--------------|19| `database-selection.md` | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database |20| `orm-selection.md` | Drizzle vs Prisma vs Kysely | Choosing ORM |21| `schema-design.md` | Normalization, PKs, relationships | Designing schema |22| `indexing.md` | Index types, composite indexes | Performance tuning |23| `optimization.md` | N+1, EXPLAIN ANALYZE | Query optimization |24| `migrations.md` | Safe migrations, serverless DBs | Schema changes |25 26---27 28## ⚠️ Core Principle29 30- ASK user for database preferences when unclear31- Choose database/ORM based on CONTEXT32- Don't default to PostgreSQL for everything33 34---35 36## Decision Checklist37 38Before designing schema:39 40- [ ] Asked user about database preference?41- [ ] Chosen database for THIS context?42- [ ] Considered deployment environment?43- [ ] Planned index strategy?44- [ ] Defined relationship types?45 46---47 48## Anti-Patterns49 50❌ Default to PostgreSQL for simple apps (SQLite may suffice)51❌ Skip indexing52❌ Use SELECT * in production53❌ Store JSON when structured data is better54❌ Ignore N+1 queries55 56## When to Use57This skill is applicable to execute the workflow or actions described in the overview.58 59## Limitations60- Use this skill only when the task clearly matches the scope described above.61- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.62- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.