What problem does it solve? Writing idiomatic Effect code requires navigating a large API surface, choosing between many equivalent patterns, and keeping error handling, dependency injection, and testing consistent. This Skill provides curated guidance, vendored source references, and opinionated conventions so Effect work in a repository follows canonical patterns instead of ad hoc solutions. ## Core Features & Use Cases - Pattern Guidance: Enforces canonical Effect patterns such as Effect.fn for business logic, Effect.gen for workflows, Schema.TaggedErrorClass for typed errors, and Context.Service with Layer for dependency injection. - Research Workflow: Directs the agent to local reference guides first, then codebase patterns, then the vendored Effect source for exact API details and behavior verification. - Package & Version Rules: Specifies installation rules such as effect@beta, aligned @effect/* package versions, and runtime-specific platform packages. - Use Case: When adding a new service with database access and retries to an Effect-based project, the Skill guides layer composition, typed error definitions, retry schedules, and @effect/vitest testing following the repository's conventions. ## Quick Start Ask the agent to implement a new Effect service with typed errors and a layer, and have it follow the Effect patterns in this repository.