Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
sickn33 avatar

Database Design

  • 1.8k installs
  • 44k repo stars
  • Updated July 27, 2026
  • sickn33/antigravity-awesome-skills

database-design is an agent skill for "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."

About

The database-design skill "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases." It covers aSK user for database preferences when unclear. Key workflows include choose database/ORM based on CONTEXT. This skill is applicable to execute the workflow or actions described in the overview. Developers invoke database-design when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.

  • ASK user for database preferences when unclear
  • Choose database/ORM based on CONTEXT
  • Don't default to PostgreSQL for everything
  • Asked user about database preference?
  • Chosen database for THIS context?

Database Design by the numbers

  • 1,803 all-time installs (skills.sh)
  • +40 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #409 of 2,184 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

database-design capabilities & compatibility

Capabilities
ask user for database preferences when unclear · choose database/orm based on context · don't default to postgresql for everything · asked user about database preference? · chosen database for this context?
Use cases
documentation
From the docs

What database-design says it does

description: "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."
SKILL.md
Learn to THINK, not copy SQL patterns.
SKILL.md
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill database-design

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.8k
repo stars44k
Security audit3 / 3 scanners passed
Last updatedJuly 27, 2026
Repositorysickn33/antigravity-awesome-skills

What problem does database-design solve for developers using the documented workflows?

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

Who is it for?

Developers working with database-design patterns described in the skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill documented scope.

When should I use this skill?

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

What you get

Actionable database-design guidance grounded in SKILL.md workflows and reference files.

  • Database recommendation
  • Indexing strategy direction

By the numbers

  • Decision tree covers 8 database options including PostgreSQL, Neon, Supabase, Turso, SQLite, pgvector, PlanetScale, and

Files

SKILL.mdMarkdownGitHub ↗

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

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.

Related skills

How it compares

Use this for early datastore selection and indexing direction rather than SQL query tuning or ORM configuration skills.

FAQ

Who is database-design for?

Developers and software engineers working with database-design patterns described in the skill documentation.

When should I use database-design?

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

Is database-design safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.