database-design

Name: database-design
Availability: InStock
Author: caobingsheng

Guide relational schema, indexing, ORM, and deployment model decisions.

1|Updated Mar 26, 2026

Search Tags:#indexing #data-modeling #schema-design #database-design #orm-selection #serverless-databases #migration-safety

Ready to run

npx skills add https://github.com/caobingsheng/skills --skill database-design-caobingsheng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/caobingsheng/skills/tree/main/design/database-design
Command: npx skills add https://github.com/caobingsheng/skills --skill database-design-caobingsheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Database design decisions can be overwhelming; teams need a structured blueprint for schema design, indexing strategy, ORM selection, and deployment models to build scalable, maintainable systems.

Core Features & Use Cases

Guidance on normalization vs denormalization, indexing strategy, and ORM considerations to align with deployment needs.
Decision checklists and anti-patterns to prevent common database design mistakes.
Use cases for relational vs serverless databases, migration planning, and performance-aware schema evolution.

Quick Start

List your deployment requirements and follow this guide to draft a robust database design plan.

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 database schema for scalability and serverless edge deployments?▼

To design a database schema for scalability, you must evaluate normalization, indexing strategies, and ORM choices to align with serverless or edge deployment models. This enforces PK/FK conventions and migration safety to prevent common design mistakes.

What is the best way to choose an ORM for a relational vs serverless database architecture?▼

Choosing an ORM for relational or serverless databases requires evaluating your deployment needs against decision checklists and anti-patterns. This ensures your ORM selection aligns with performance-aware schema evolution and avoids defaulting to a single database.

How do I plan migration safety for performance-aware schema evolution?▼

Planning migration safety for schema evolution involves using decision checklists to guide normalization vs denormalization and indexing strategy. This prevents common database design mistakes while ensuring performance-aware schema evolution across diverse environments.

When do I need to normalize or denormalize data models for robust database architectures?▼

You need to normalize or denormalize data models when building robust database architectures that require specific indexing strategies and ORM considerations. This decision aligns your schema design with deployment needs and prevents performance bottlenecks.

Does this database design guidance default to a specific database or platform?▼

This database design guidance does not default to a specific database or platform. It covers projects evaluating relational schemas, indexing strategies, and serverless or edge deployments across diverse environments without locking you into one system.