database-design

Guide engineers in designing scalable database schemas and choosing SQL or NoSQL.

3|4|Updated Mar 20, 2026

Search Tags:#indexing #optimization #schema #migration #sql #nosql #database-design

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide engineers in designing scalable database schemas and choosing between SQL and NoSQL.

Core Features & Use Cases

Principles: normalization, indexing strategy, migrations
Use cases: designing schemas, migrations, vector DB integration, ORM
Example: craft a migration plan for a multi-tenant app

Quick Start

Design a scalable relational schema for a blogging platform with users, posts, and comments.

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 scalable database schema for a multi-tenant application?▼

To design a scalable database schema for a multi-tenant app, you need a structured migration plan that defines tenant isolation, normalization boundaries, and indexing strategies to ensure performance as data grows. This process involves choosing appropriate relationships and applying schema design principles tailored to your specific architecture.

When should I choose SQL vs NoSQL for my application's schema design?▼

Choosing SQL vs NoSQL for schema design depends on your data structure and scaling requirements. SQL like PostgreSQL provides strict normalization and relational integrity, while NoSQL like MongoDB offers flexible schemas for rapid iteration, and Redis handles high-speed caching workloads.

What's the best way to plan a safe database migration without downtime?▼

The best way to plan a safe database migration without downtime is to apply migration safety patterns that ensure backward compatibility. This involves incrementally updating your schema, optimizing indexing strategies concurrently, and validating data integrity across PostgreSQL or MongoDB environments before final cutover.

How does query optimization and indexing strategy work in PostgreSQL?▼

Query optimization and indexing strategy in PostgreSQL works by structuring your schema and indexes to minimize scan times and maximize retrieval efficiency. Proper indexing targets specific query patterns, leveraging normalization principles to maintain relationships while tuning performance for large datasets.

Can I integrate vector database capabilities into my existing relational schema?▼

Yes, you can integrate vector database capabilities into a relational schema by applying specific design patterns that bridge structured data and vector embeddings. This involves extending your PostgreSQL schema with specialized indexing strategies to support similarity searches alongside traditional relational queries.

What are the limitations of relying on ORM integration for schema migrations?▼

Limitations of relying on ORM integration for schema migrations include potential performance bottlenecks during large data transformations and restricted control over advanced indexing or query optimization. Complex relationships or multi-tenant architectures often require manual SQL or NoSQL schema design to ensure migration safety and proper tuning.