What problem does it solve? Making outbound HTTP calls in TypeScript often means untyped responses, ad-hoc retry logic, scattered auth handling, and raw fetch calls leaking into business code. This Skill guides an agent to build outgoing HTTP integrations with Effect's HttpClient so requests, responses, errors, retries, and transports are all typed and composable. ## Core Features & Use Cases - Typed request/response pipeline: Build immutable HttpClientRequest values, execute them through a configured HttpClient service, and decode bodies with Schema via schemaBodyJson, schemaJson, and matchStatus. - Resilience combinators: Apply retryTransient for transient statuses, Effect.timeout for deadlines, withRateLimiter for client-side rate limiting, cookie jars, redirect following, and tracing spans. - Transport layers and error taxonomy: Choose FetchHttpClient or NodeHttpClient (undici/node:http) transports and handle failures through the single HttpClientError wrapper with its reason union. - Use Case: Wrap a third-party REST API in a named service that prepends the base URL, attaches a redacted bearer token, filters non-2xx statuses, retries transient failures three times, and decodes responses into Schema classes. ## Quick Start Ask the agent to write an Effect service that calls an external REST API using HttpClient with schema-decoded responses, typed errors, and retry on transient failures.
