What problem does it solve? Frontend routes often need data shaped differently from domain DTOs, and stitching multiple API calls in the UI causes N+1 requests and duplicated logic. This Skill guides the creation of read-only query use cases in the BFF (Backend for Frontend) style, with language-specific playbooks for TypeScript and Go. ## Core Features & Use Cases - BFF Query Use Cases (TypeScript): Build Handler classes in the ui context that query tables directly via Drizzle, with Zod input/output schemas, pagination, joins, aggregations, and outputSchema.parse() on return. - Ctx-Local Go Queries: Implement Go Handler[I,O] query handlers that read from repositories without UnitOfWork, with pagination defaults and primitive output mapping. - Language Dispatch: Routes to the TypeScript or Go playbook by file extension, enforcing the ownership rule that UI-shaped queries live in api-typescript while Go owns only ctx-local reads. - Use Case: When a dashboard page needs patient counts, appointments, and revenue in one round-trip, scaffold a single composite query use case instead of three frontend fetches. ## Quick Start Ask the agent to create a UI query use case for the data your route needs, for example: create a ListPatients query with name filter and pagination in the ui context.