database-design

Structured guidance for database selection, schema design, and query optimization decisions. Learn to THINK, not copy SQL patterns. Read ONLY files relevant to the request! Check the content map, find what you need. Before designing schema: ❌ 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 This skill is applicable to execute the workflow or actions described in the overview. - Covers six core areas: database selection (PostgreSQL, Neon, Turso, SQLite), ORM choice (Drizzle, Prisma, Kysely), schema normalization, indexing strategy, query optimization, and safe migrations - Emphasizes context-driven decision-making rather than defaulting to PostgreSQL; includes a checklist for schema design prerequisites - Highlights common anti-patterns: unnecessary PostgreSQL adoption, missing indexes, SELECT * in production, JSON overuse, and N+1 queries - Organized as a modular reference with a content map directing you to relevant files based on your specific task - ASK user for database preferences when unclear - Choose database/ORM based on CONTEXT - Don't default to PostgreSQL for everything - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert...