0db870eb11
Add a maintainers script to safely promote high-confidence legacy risk labels from unknown to concrete values, cover it with tests, and regenerate the canonical skill artifacts and plugin copies. This reduces the legacy unknown backlog without forcing noisy classifications that still need manual review.
58 lines
1.6 KiB
Markdown
58 lines
1.6 KiB
Markdown
---
|
|
name: database-design
|
|
description: "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."
|
|
risk: safe
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# 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.
|