database-design
starsforks
How to install database-design?
one-man-company/skills-contextmanager/database-design
$npx -y skills add One-Man-Company/Skills-ContextManager --skill database-designDatabase design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
SKILL.md
| 1 | # Database Design |
| 2 | |
| 3 | > **Learn to THINK, not copy SQL patterns.** |
| 4 | |
| 5 | ## 🎯 Selective Reading Rule |
| 6 | |
| 7 | **Read ONLY files relevant to the request!** Check the content map, find what you need. |
| 8 | |
| 9 | | File | Description | When to Read | |
| 10 | |------|-------------|--------------| |
| 11 | | `database-selection.md` | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database | |
| 12 | | `orm-selection.md` | Drizzle vs Prisma vs Kysely | Choosing ORM | |
| 13 | | `schema-design.md` | Normalization, PKs, relationships | Designing schema | |
| 14 | | `indexing.md` | Index types, composite indexes | Performance tuning | |
| 15 | | `optimization.md` | N+1, EXPLAIN ANALYZE | Query optimization | |
| 16 | | `migrations.md` | Safe migrations, serverless DBs | Schema changes | |
| 17 | |
| 18 | --- |
| 19 | |
| 20 | ## ⚠️ Core Principle |
| 21 | |
| 22 | - ASK user for database preferences when unclear |
| 23 | - Choose database/ORM based on CONTEXT |
| 24 | - Don't default to PostgreSQL for everything |
| 25 | |
| 26 | --- |
| 27 | |
| 28 | ## Decision Checklist |
| 29 | |
| 30 | Before designing schema: |
| 31 | |
| 32 | - [ ] Asked user about database preference? |
| 33 | - [ ] Chosen database for THIS context? |
| 34 | - [ ] Considered deployment environment? |
| 35 | - [ ] Planned index strategy? |
| 36 | - [ ] Defined relationship types? |
| 37 | |
| 38 | --- |
| 39 | |
| 40 | ## Anti-Patterns |
| 41 | |
| 42 | ❌ Default to PostgreSQL for simple apps (SQLite may suffice) |
| 43 | ❌ Skip indexing |
| 44 | ❌ Use SELECT * in production |
| 45 | ❌ Store JSON when structured data is better |
| 46 | ❌ Ignore N+1 queries |
People who liked this also viewed
6 picksType
- azure-storageAzure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier,SkillsJul 2026
- supabase-postgres-best-practicesPostgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.SkillsJul 2026
- supabaseUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, SkillsJul 2026
- convex-quickstartCreates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.SkillsJul 2026
- convex-performance-auditAudits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.SkillsJul 2026
- convex-setup-authSets up Convex auth, identity mapping, and access control. Use for login, auth providers, users tables, protected functions, or roles in a Convex app.SkillsJul 2026
