database-design▌
sickn33/antigravity-awesome-skills · updated Apr 8, 2026
Structured guidance for database selection, schema design, and query optimization decisions.
- ›Covers six core areas: database selection (PostgreSQL, Neon, Turso, SQLite), ORM choice (Drizzle, Prisma, Kysely), schema normalization, indexing strategy, query optimization, and safe migrations
- ›Emphasizes context-driven decision-making rather than defaulting to PostgreSQL; includes a checklist for schema design prerequisites
- ›Highlights common anti-patterns: unnecessary PostgreSQL adoption,
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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★55 reviews- ★★★★★Isabella Gonzalez· Dec 28, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ren Rao· Dec 16, 2024
database-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ava Dixit· Dec 12, 2024
Solid pick for teams standardizing on skills: database-design is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Dec 8, 2024
Solid pick for teams standardizing on skills: database-design is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Nov 27, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Jain· Nov 19, 2024
Solid pick for teams standardizing on skills: database-design is focused, and the summary matches what you get after install.
- ★★★★★Ren Ramirez· Nov 7, 2024
database-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Alexander Verma· Nov 3, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ren Menon· Oct 26, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Tariq Thompson· Oct 22, 2024
database-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 55