multiAI Summary Pending
database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/database-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/database-design/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/database-design/SKILL.mdinside your project - Restart your AI agent ā it will auto-discover the skill
How database-design Compares
| Feature / Agent | database-design | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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