database-design

Guide database selection, schema design, indexing, ORM choices, and migrations.

3|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/Harmitx7/tribunal-kit --skill database-design-harmitx7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/Harmitx7/tribunal-kit/tree/main/.agent/skills/database-design
Command: npx skills add https://github.com/Harmitx7/tribunal-kit --skill database-design-harmitx7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical challenge of designing efficient, scalable, and maintainable database schemas, preventing costly errors and performance bottlenecks.

Core Features & Use Cases

  • Database Selection: Guides you in choosing the right database technology (PostgreSQL, MongoDB, Redis, etc.) based on your application's specific needs.
  • Schema Design: Provides best practices for naming conventions, primary keys, timestamps, and relationships to ensure data integrity and ease of use.
  • Indexing Strategy: Offers guidance on when and how to create indexes to optimize query performance without over-indexing.
  • ORM Selection: Helps in choosing the appropriate Object-Relational Mapper (ORM) for your project.
  • Migration Best Practices: Outlines safe strategies for database schema migrations to prevent downtime and data loss.
  • Vector Database Patterns: Includes patterns for integrating vector embeddings for AI applications using pgvector.

Quick Start

Use the database-design skill to help select the most appropriate database for a new e-commerce application that requires strong transactional integrity and handles a moderate amount of user-generated content.

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 and prevent performance bottlenecks?

Designing a scalable database schema requires applying best practices for naming conventions, primary keys, timestamps, and relationships. This approach ensures data integrity and prevents costly performance bottlenecks during application development.

What's the best way to choose between PostgreSQL and NoSQL databases for my application?

Choosing between PostgreSQL and NoSQL databases depends on your application's specific needs. You should evaluate transactional integrity requirements, data relationships, and query patterns to select the right technology for strong consistency or flexible scaling.

How do I create an indexing strategy to optimize SQL query performance without over-indexing?

To optimize SQL query performance, you must carefully evaluate when and how to create indexes based on your query patterns. This prevents over-indexing while ensuring the database efficiently retrieves data for your application.

How do I execute safe database schema migrations without causing downtime or data loss?

Executing safe database schema migrations requires following specific best practices and strategies. These safe migration patterns prevent downtime and data loss when altering relational database structures during application updates.

Can I use PostgreSQL to store and query vector embeddings for AI applications?

Yes, you can use PostgreSQL to store and query vector embeddings for AI applications. By integrating pgvector patterns, you can handle vector data directly within your relational database for AI-driven search functionality.

How do I select the appropriate ORM for my project's database design?

Selecting the appropriate Object-Relational Mapper (ORM) involves evaluating your project's specific database schema, query complexity, and performance requirements. Choosing the right ORM ensures maintainable data interactions within your application.