sql-query-conventions

What problem does it solve?

This Skill prevents slow, costly, and subtly incorrect data-access patterns in read-path queries by enforcing practical SQL/PostgREST/ORM conventions that scale as your data grows.

Core Features & Use Cases

• List-query safety: Enforces explicit limits, stable ordering for pagination, and correct single-row semantics to avoid unbounded reads and paging bugs.
• Anti–N+1 guidance: Detects and prevents per-item async fetch loops by recommending batching, joins, or server-side aggregation approaches.
• Bandwidth and correctness focus: Promotes explicit column selection instead of SELECT * to reduce coupling to schema growth and limit over-fetching.

Use it when you are reviewing or generating SELECT queries, PostgREST .from()/.select() chains, list-returning ORM calls, or pagination designs, especially for user-facing endpoints and background jobs that will hit real data volumes.

Quick Start

Apply the sql-query-conventions rules to the proposed SELECT query and point out any violations of limit, pagination ordering, N+1 patterns, and column selection.