database-design

Name: database-design
Author: sickn33

Structured guidance for database selection, schema design, and query optimization decisions. 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

INSTALLATION

npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill database-design

Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$2a

⚠️ 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.

Limitations

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 review.

Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.