What problem does it solve? Writing production-grade TypeScript with Effect v4 requires choosing correctly among many APIs—services, layers, schemas, schedules, caches, streams, and HTTP clients—and misusing them leads to fragile retries, hand-rolled caches, flaky tests, and untyped errors. This Skill provides opinionated, branch-specific guidance so Effect code follows current v4 conventions from the start. ## Core Features & Use Cases - Branch-specific reference routing: Directs the AI to read only the relevant reference file (schema, services/layers, config, scheduling, caching, streams, HTTP clients, or testing) based on the task. - Production defaults and anti-patterns: Enforces conventions like Effect.fn operation boundaries, Schema.TaggedError for typed failures, Config instead of process.env, and TestClock instead of real sleeps, with explicit Do Nots. - Use Case: When implementing a polling worker that calls a rate-limited provider API, the Skill guides you to use Schedule with jittered backoff, retryAfterMs-aware delays, typed pass failures, and Cache for deduplicating concurrent lookups. ## Quick Start Use the effect skill to implement a new service with a layer, typed errors, and retry logic in my Effect v4 TypeScript project.