database-design

Name: database-design
Availability: InStock
Author: AnvinX1

Design normalized relational database schemas with primary keys and indexing strategies.

Updated Feb 12, 2026

Search Tags:#design #indexing #database #serverless #schema #orm #normalization

Ready to run

npx skills add https://github.com/AnvinX1/med-rag --skill database-design-anvinx1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/AnvinX1/med-rag/tree/main/medical_genai_app/.agent/skills/database-design
Command: npx skills add https://github.com/AnvinX1/med-rag --skill database-design-anvinx1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Design robust, scalable database schemas.

Core Features & Use Cases

Core principle: Choose appropriate database and modeling approaches to avoid over/under-normalization.
Use Case: When designing a new app, define normalization, PKs, relationships, indexing strategy, and migration plan to support scalable queries.
Anti-patterns: Avoid leaky abstractions and database-agnostic pitfalls; ensure alignment with deployment environment.

Quick Start

Start by analyzing a data domain and define a normalized relational schema with clear PKs and indexing strategy.

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 for a new application?▼

To design a normalized database schema, analyze your data domain to define relationships, primary keys, and indexing strategies that prevent over or under-normalization and support scalable queries.

What is the best way to choose an indexing strategy for serverless databases?▼

Choosing an indexing strategy for serverless databases involves aligning indexes with your deployment environment to prevent leaky abstractions and ensure scalable query performance.

How do I plan safe database migrations for ORM models?▼

Plan safe database migrations by defining timestamp strategies, primary key selection, and foreign keys upfront, ensuring ORM choices align with your deployment environment to avoid database-agnostic pitfalls.

When should I use normalization versus denormalization in relational models?▼

Use normalization in relational models to ensure data integrity, but avoid over-normalization by choosing appropriate modeling approaches that still support efficient, scalable queries.

Does ORM selection affect database indexing and schema design?▼

ORM selection directly affects database indexing and schema design because poor ORM choices can cause leaky abstractions and database-agnostic pitfalls that harm query performance and migration safety.

What primary key and timestamp strategies should I use for scalable schemas?▼

Select primary keys and timestamp strategies that match your relational model and deployment environment, ensuring robust schema design and safe migrations across serverless and traditional databases.