postgres-index-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 and requires deployed-version, extension, collation, partition, and provider checks. The optional Python 3.11 helper reads an exported JSON inventory only and reports conservative structural signals. ## Use this skill when - A constraint or representative statement family has established a need for a new or changed index. - Key order, access method, operator class, collation, sort direction, INCLUDE payload, partial predicate, or expression needs design. - Potentially duplicate or overlapping indexes need conservative structural and workload review. - A unique, covering, specialized, partition-local, or concurrently built index needs a verification and cost model. ## Do not use this skill when - The source of query latency is not established; use `postgres-query-performance-review` first. - The task is a broad schema or privilege audit; use `postgres-schema-review`. - The exact index is already approved and only production sequencing remains; use `postgres-migration-safety`. - The task is greenfield domain modeling without plan evidence; use `postgres-schema-design`. ## Inputs Inspect or obtain: - PostgreSQL version/provider, extensions/operator classes, collation, partitioning, and current settings that affect planning. - Constraint or sa