What problem does it solve? List endpoints, dropdowns, and pickers that fetch entire tables work fine against seed data but collapse in production when a table holds tens of thousands of rows per tenant. This Skill enforces query shapes that scale from day one, avoiding painful rewrites of both the database query and the UI contract later. ## Core Features & Use Cases - Bounded list queries: Enforces server-clamped limits, tenant-scoped WHERE clauses over indexed columns, and keyset (cursor) pagination instead of offset pagination. - Search-as-you-type pickers: Defines a pattern for typeahead endpoints with debounced client requests, AbortController cancellation, hard result caps, and per-group caps for multi-entity search. - Free-text query support: Ensures every list function accepts a case-insensitive query across natural keys like name or email so callers can find rows instead of paging to them. - Use Case: When building a Prisma-backed Next.js combobox that lists all customers for a tenant, apply this Skill to replace a fetch-all-then-filter approach with a capped, cursor-paginated, tenant-scoped search endpoint. ## Quick Start Review my customer picker endpoint and rewrite it to use keyset pagination with a capped, tenant-scoped search query.
