Database Design
SkillDatabases & dataThe database design skill is a skill that gives an AI agent reference guides for database design decisions. It covers choosing a database, comparing ORMs, schema normalization, indexing strategies, query optimization, and safe migrations. The agent reads only the guide relevant to your question and asks about your database preferences before deciding.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent environment that supports skills and the Read, Write, Edit, Glob, and Grep tools.
Then ask your AI: use the Database Design skill
What your AI can do with it
- Compare database options: PostgreSQL, Neon, Turso, and SQLite
- Compare ORMs: Drizzle, Prisma, and Kysely
- Design schemas with normalization, primary keys, and relationships
- Plan indexing strategies, including index types and composite indexes
- Optimize queries by addressing N+1 problems and using EXPLAIN ANALYZE
- Plan safe migrations, including for serverless databases
Getting started
- Have an agent environment that supports skills and the Read, Write, Edit, Glob, and Grep tools.
- Add the database-design skill to your agent's available skills.
- Ask your agent a database question, such as choosing a database, an ORM, or designing a schema.
- Answer the agent's questions about your database preferences so it can decide based on your context.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/development/database-design/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Sep 2026
Others that do the same job
Questions
- Does the agent read every guide at once?
- No. The skill instructs the agent to check the content map and read only the file relevant to the request, such as indexing.md for performance tuning or migrations.md for schema changes.
- Which database does it recommend?
- It does not default to any database. It chooses based on your context and deployment environment, and asks about your preferences when unclear. For simple apps, SQLite may suffice instead of PostgreSQL.
- What anti-patterns does it warn against?
- Defaulting to PostgreSQL for simple apps, skipping indexing, using SELECT * in production, storing JSON when structured data is better, and ignoring N+1 queries.
Advanced
- Item type
- skill
- Key
database-design-davila7- Source
- github.com/davila7/claude-code-templates