postgres-schema-designlisted

# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Guidance targets PostgreSQL 18; check it against the deployed major version, extensions, collations, and managed-service limits. The optional DDL scanner requires Python 3.11, reads local text only, and is heuristic. ## Use this skill when - A new PostgreSQL-backed product, service, or bounded context needs a relational model. - Domain invariants, tenant boundaries, lifecycle rules, or retention requirements must become database constraints. - Keys, types, nullability, relationships, RLS, partitioning, and index intent need one coherent proposal. - An existing model is being substantially reshaped and the target design must be stated before migration planning. ## Do not use this skill when - The task is to rank defects in an already deployed schema or DDL snapshot; use `postgres-schema-review`. - The task is to interpret a plan for one or more slow statements; use `postgres-query-performance-review`. - The desired index follows from measured query plans; use `postgres-index-design`. - The target schema is already decided and the problem is safe rollout; use `postgres-migration-safety`. ## Inputs Inspect or obtain: - PostgreSQL major version, provider, extensions, collations, and operational constraints. - Domain entities, business identities, invariants, lifecycle owner