api-integrationlisted

# Purpose Produce tested integration code for connecting the layers of the platform: REST route handlers in the main app (project.json -> `mainApp`), ORM database queries, server-side WebSocket clients that subscribe to device/edge telemetry (project.json -> `device`), and SSE endpoints that fan out real-time data to browsers. All generated code follows the project's conventions (lazy DB init, Auth.js session checks, Zod validation at boundaries). The code patterns below are illustrated with Drizzle ORM -- adapt them to the project's actual ORM (check `CLAUDE.md` and project.json -> `stack.db`). # When to use - Implementing a new API route handler (`src/app/api/**/route.ts`) in the main app - Writing an ORM query (select, insert, update, delete) in a Server Component or route handler - Connecting the main app to a device/edge WebSocket endpoint for telemetry ingestion - Creating or modifying an SSE streaming endpoint or a client-side `EventSource` hook # When NOT to use - Modifying the ORM schema definition itself without implementing queries (use `api-contract`) - Writing or modifying deployment manifests or infrastructure code (use `deployment`) - Writing firmware/edge code for the device repo (use the device-domain skills from the project's enabled packs) - Reviewing existing code for style or quality (use `code-standards` or `code-quality`) - Adding observability instrumentation (metrics, tracing) to an endpoint (compose with `observability`) # Required environment