vudovn

database-design

@vudovn/database-design
vudovn
972
202 forks
Updated 1/18/2026
View on GitHub

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

Installation

$skills install @vudovn/database-design
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Path.agent/skills/database-design/SKILL.md
Branchmain
Scoped Name@vudovn/database-design

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


name: database-design description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. allowed-tools: Read, Write, Edit, Glob, Grep

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.

FileDescriptionWhen to Read
database-selection.mdPostgreSQL vs Neon vs Turso vs SQLiteChoosing database
orm-selection.mdDrizzle vs Prisma vs KyselyChoosing ORM
schema-design.mdNormalization, PKs, relationshipsDesigning schema
indexing.mdIndex types, composite indexesPerformance tuning
optimization.mdN+1, EXPLAIN ANALYZEQuery optimization
migrations.mdSafe migrations, serverless DBsSchema 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