Agent skill · data analytics · davila7
database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Why this skill is useful
Provides domain-specific knowledge on schema design, indexing strategies, and ORM selection that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
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. File Description When to Read ------ ------------- -------------- database-selection.md PostgreSQL vs Neon vs Turso vs SQLite Choosing database orm-selection.md Drizzle vs Prisma vs Kysely Choosing ORM schema-design.md Normalization, PKs, relationships Designing schema indexing.md Index types, composite indexes Performance tuning optimization.md N+1, EXPLAIN ANALYZE Query optimization migrations.md Safe migrations, serverless DBs Schema 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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/database-design