How do I install database-design?

Run `npx skills add https://github.com/davila7/claude-code-templates --skill database-design` in your terminal. You need to have run `npx skills init` once in your project first.

Which agent frameworks does database-design support?

database-design works with any agent framework supported by the Skills registry, including Claude Code, Cursor, GitHub Copilot, Cline, Codex, and Gemini CLI.

Is database-design free to use?

Yes. database-design is free to install and use. It is available from the open explainx.ai skill registry published by davila7.

Where can I read ratings and reviews for database-design?

Community ratings and review text appear on this explainx.ai skill page below the description. Reviews use a 1–5 scale and may include short written feedback from signed-in members.

Frontend

database-design▌

davila7/claude-code-templates · updated Apr 8, 2026

$npx skills add https://github.com/davila7/claude-code-templates --skill database-design

0 commentsdiscussion

summary

Learn to THINK, not copy SQL patterns.

skill.md

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

Discussion

Product Hunt–style comments (not star reviews)

No comments yet — start the thread.

general reviews

Ratings

4.7★★★★★29 reviews

★★★★★Nia Abbas· Dec 24, 2024
I recommend database-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
★★★★★Rahul Santra· Sep 25, 2024
I recommend database-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
★★★★★Sakshi Patil· Sep 17, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
★★★★★Hana Anderson· Sep 13, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
★★★★★Anaya Harris· Sep 1, 2024
database-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
★★★★★Anika Reddy· Aug 20, 2024
We added database-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
★★★★★Pratham Ware· Aug 16, 2024
Useful defaults in database-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
★★★★★Mia Singh· Aug 12, 2024
Useful defaults in database-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
★★★★★Chaitanya Patil· Aug 8, 2024
database-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
★★★★★Hana Gonzalez· Aug 4, 2024
database-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 29

1 / 3