What problem does it solve? Building HTTP APIs in TypeScript often means duplicating route definitions, validation logic, OpenAPI docs, and client code that drift out of sync. This Skill guides the creation of a single typed API definition with Effect v4's HttpApi module so the server, documentation, and derived client all stay consistent. ## Core Features & Use Cases - Schema-First Endpoint Definitions: Define endpoints with typed params, query strings, headers, payloads, success responses, and tagged errors, including content negotiation and multipart file uploads. - Middleware and Security: Implement bearer, basic, API key, and custom security schemes as typed middleware layers, plus schema-error transforms for validation responses. - Derived Clients, Docs, and Tests: Generate OpenAPI specifications, Swagger/Scalar docs, fully typed HTTP clients, and handler unit tests from the same definition. - Use Case: Define a Users API group with CRUD endpoints and bearer authentication once, then serve it on Node.js, expose OpenAPI docs at /docs, and hand frontend teams a type-safe client without writing any client code. ## Quick Start Use the effect-http-api skill to scaffold a typed Effect v4 HTTP API with a users endpoint group, bearer auth middleware, and OpenAPI docs.
