database-design

Design normalized database schemas with indexing and migration strategies.

8.1k|1.5k|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/vudovn/antigravity-kit --skill database-design-vudovn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/vudovn/antigravity-kit/tree/main/.agent/skills/database-design
Command: npx skills add https://github.com/vudovn/antigravity-kit --skill database-design-vudovn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers to design robust, efficient, and maintainable database schemas by providing principled guidance on normalization, keys, indexing, and migrations.

Core Features & Use Cases

  • Schema design guidance: normalization vs denormalization, primary/foreign key strategies, and relationship modeling.
  • Indexing and performance planning: indexing strategies, composite keys, and read/write trade-offs.
  • ORM and deployment choices: recommendations for ORM selections and serverless database options across different environments. Use Case: When starting a new application, use this Skill to outline a normalized schema, an indexing plan, and a migration strategy before writing code.

Quick Start

Start by drafting a normalized schema with primary keys and an initial indexing plan for a sample app.

Frequently Asked Questions about database-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a normalized database schema with primary and foreign keys?

To design a normalized database schema, apply principled guidelines for primary and foreign key strategies, relationship modeling, and timestamp conventions to ensure data integrity and maintainability across varying project scales.

What's the best way to plan indexing strategies and composite keys for a new application?

The best way to plan indexing strategies is to evaluate read/write trade-offs and apply composite keys to optimize database performance, ensuring efficient query execution across your application's schema design.

When do I need database normalization versus denormalization in schema design?

You need database normalization versus denormalization when balancing data integrity against query performance, applying schema design principles to decide the optimal structure based on your specific application requirements and scale.

How do I choose an ORM and serverless database for my project scale?

To choose an ORM and serverless database, evaluate deployment choices and project scale requirements, applying recommendations that match your specific environment and performance needs for optimal database design.

What are safe migration patterns for updating an existing database schema?

Safe migration patterns for database schema updates involve applying structured guidelines to enforce normalization decisions, primary and foreign key constraints, and timestamp conventions without disrupting existing data integrity.