database-schema-designlisted

# Database Schema Design ## When to use this skill Lists specific situations where this skill should be triggered: - **New Project**: Database schema design for a new application - **Schema Refactoring**: Redesigning an existing schema for performance or scalability - **Relationship Definition**: Implementing 1:1, 1:N, N:M relationships between tables - **Migration**: Safely applying schema changes - **Performance Issues**: Index and schema optimization to resolve slow queries ## Input Format The required and optional input information to collect from the user: ### Required Information - **Database Type**: PostgreSQL, MySQL, MongoDB, SQLite, etc. - **Domain Description**: What data will be stored (e.g., e-commerce, blog, social media) - **Key Entities**: Core data objects (e.g., User, Product, Order) ### Optional Information - **Expected Data Volume**: Small (<10K rows), Medium (10K-1M), Large (>1M) (default: Medium) - **Read/Write Ratio**: Read-heavy, Write-heavy, Balanced (default: Balanced) - **Transaction Requirements**: Whether ACID is required (default: true) - **Sharding/Partitioning**: Whether large data distribution is needed (default: false) ### Input Example ``` Design a database for an e-commerce platform: - DB: PostgreSQL - Entities: User, Product, Order, Review - Relationships: - A User can have multiple Orders - An Order contains multiple Products (N:M) - A Review is linked to a User and a Product - Expected data: 100,000 users, 10,000 products