What problem does it solve? Writing idiomatic Effect code is hard because the library offers many ways to accomplish the same task, and teams struggle to apply consistent patterns for error handling, dependency injection, and testing across a codebase. ## Core Features & Use Cases - Effect Pattern Guidance: Provides curated guides for core Effect usage, error handling, layers, observability, retries, schedules, schemas, SQL, and testing. - Vendored Source Research: Directs research into a local vendored Effect repository for exact API signatures and implementation details when guides are insufficient. - Installation & Versioning Rules: Enforces aligned effect@beta and @effect/* package versions matched to the target runtime (Node, Browser, Bun, Vitest). - Use Case: When adding a new service to an Effect-based project, the Skill ensures you define it with Context.Service, build it with Layer.effect, handle failures with Schema.TaggedErrorClass, and provide layers only at the application boundary. ## Quick Start Ask the assistant to implement a new Effect service with typed error handling and layer-based dependency injection following this repository's Effect conventions.