What problem does it solve? Designing a PostgreSQL schema involves many database-specific decisions—data types, indexing strategies, constraints, partitioning, and row-level security—where wrong choices cause performance problems and maintenance debt that are hard to fix later. ## Core Features & Use Cases - Schema Design Guidance: Covers primary keys, normalization to 3NF, NOT NULL and CHECK constraints, and foreign key indexing rules specific to PostgreSQL behavior. - Data Type & Index Selection: Recommends correct types (TIMESTAMPTZ, NUMERIC, TEXT, JSONB, arrays, ranges) and index strategies (B-tree, GIN, GiST, BRIN, partial, covering, expression indexes). - Scale & Safety Patterns: Addresses partitioning, row-level security, update-heavy and insert-heavy workloads, upserts, and safe schema evolution with transactional DDL. - Use Case: When building a new orders table, use this Skill to choose identity columns, enforce status CHECK constraints, index the foreign key on user_id, and plan time-based partitioning for growth. ## Quick Start Ask the AI to design a PostgreSQL schema for your application's tables following best practices for data types, indexes, and constraints.