database-design
sickn33/antigravity-awesome-skills
Database design principles and decision-making for schema, indexing, ORM selection, and serverless databases.
What is database-design?
This skill guides you through database design decisions including schema normalization, indexing strategies, ORM selection, and database choice. Use it when architecting data models, optimizing queries, or choosing between PostgreSQL, SQLite, Neon, Turso, and ORMs like Drizzle, Prisma, or Kysely.
- Choose appropriate database for your context (PostgreSQL, SQLite, Neon, Turso)
- Select and configure ORM (Drizzle, Prisma, Kysely)
- Design normalized schemas with proper relationships and primary keys
- Plan and implement indexing strategies for performance
- Optimize queries and identify N+1 problems
- Execute safe schema migrations for serverless environments
How to install database-design
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill database-designHow to use database-design
- 1.Identify your database preference or ask the user if unclear
- 2.Check the content map to find relevant files (database-selection.md, orm-selection.md, schema-design.md, indexing.md, optimization.md, migrations.md)
- 3.Read only files relevant to your specific task
- 4.Apply the decision checklist before designing schema
- 5.Avoid anti-patterns like defaulting to PostgreSQL for simple apps or skipping indexes
Use cases
- Architecting a new application database schema from requirements
- Selecting between PostgreSQL and SQLite for a simple app
- Optimizing slow queries using EXPLAIN ANALYZE
- Choosing an ORM that fits your deployment environment
- Planning indexes for high-traffic tables
- Backend developers designing new systems
- Full-stack developers choosing database technology
- DevOps engineers planning database infrastructure
- Teams migrating between database systems
database-design FAQ
No. Choose based on context. SQLite may suffice for simple apps; Neon or Turso for serverless; PostgreSQL for complex applications with advanced features.
Refer to orm-selection.md. Consider your deployment environment, type safety needs, and query complexity. Each has different strengths.
Defaulting to SELECT * in production and ignoring N+1 query problems. Always specify columns and optimize query patterns.
Plan index strategy before deployment. Index frequently queried columns, foreign keys, and composite indexes for multi-column filters. Use EXPLAIN ANALYZE to verify.
Use the migrations.md guidance for safe, reversible migrations. Serverless databases have specific constraints—plan accordingly.
Full instructions (SKILL.md)
Source of truth, from sickn33/antigravity-awesome-skills.
name: database-design description: "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases." risk: safe source: community date_added: "2026-02-27"
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.
| File | Description | When to Read |
|---|---|---|
database-selection.md | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database |
orm-selection.md | Drizzle vs Prisma vs Kysely | Choosing ORM |
schema-design.md | Normalization, PKs, relationships | Designing schema |
indexing.md | Index types, composite indexes | Performance tuning |
optimization.md | N+1, EXPLAIN ANALYZE | Query optimization |
migrations.md | Safe migrations, serverless DBs | Schema 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
More from sickn33/antigravity-awesome-skills and the wider catalog.
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
discord-bot-architect
Specialized skill for building production-ready Discord bots.
doc-coauthoring
This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
docker-expert
Advanced Docker expert for container optimization, security hardening, multi-stage builds, and production deployment strategies.
documentation-templates
Ready-to-use templates for README, API docs, code comments, and AI-friendly documentation.
email-systems
Email has the highest ROI of any marketing channel. $36 for every