database-design

Guide database schema design with indexing and migration strategies.

Updated Mar 18, 2026

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

Ready to run

npx skills add https://github.com/raccioly/coach-gravity --skill database-design-raccioly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/raccioly/coach-gravity/tree/main/content/starter-kit/skills/database-design
Command: npx skills add https://github.com/raccioly/coach-gravity --skill database-design-raccioly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design robust, scalable databases by applying principled guidance on schema design, indexing, ORM selection, and serverless options to prevent common pitfalls.

Core Features & Use Cases

Clear decision criteria for normalization vs denormalization, primary key strategy, and migration patterns.
Guidance on timestamps, foreign keys, and indexing strategies for high-velocity apps.
Use case: when starting a new product, decide between PostgreSQL, Neon, or Turso and pick an appropriate ORM (Prisma or Drizzle).

Quick Start

Outline your data domains and select a database plus ORM based on deployment needs and DX.

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

When deciding between PostgreSQL, Neon, or Turso, evaluate your deployment needs and developer experience. Selecting the right database involves matching serverless options with appropriate ORM choices like Prisma or Drizzle for scalable apps.

What's the best way to choose between Prisma and Drizzle for my database ORM?▼

Choosing between Prisma and Drizzle depends on your specific deployment needs and developer experience. Both ORMs integrate well with PostgreSQL, Neon, and Turso, providing robust schema design and migration support for scalable applications.

When should I use normalization versus denormalization in my database schema?▼

Use normalization to ensure data integrity in complex relational schemas, while denormalization suits high-velocity read-heavy apps. Clear decision criteria help balance these approaches based on foreign keys, timestamps, and indexing strategies.

How do I ensure zero-downtime database migrations when updating a schema?▼

Zero-downtime database migrations require enforcing specific migration patterns and guardrails. By applying principled schema design and best practices, you can update tables, timestamps, and relationships without disrupting high-velocity applications.

Does this database design guidance support both PostgreSQL and serverless platforms like Turso?▼

Yes, this guidance supports both PostgreSQL and serverless platforms like Turso and Neon. It covers vendor and tool choices across these environments, ensuring your schema design, indexing, and ORM selections fit your platform context.