What problem does it solve? Effect v4 code that acquires resources like connections, file handles, or event listeners needs guaranteed cleanup, but the v4 Scope API differs substantially from v3 and most training data, causing leaks, premature releases, and compile errors from renamed APIs. ## Core Features & Use Cases - Scoped acquisition: Guides correct use of Effect.acquireRelease, acquireDisposable, acquireUseRelease, and addFinalizer so cleanup always runs on success, failure, or interruption. - Scope elimination and ownership: Explains Effect.scoped, scopedWith, Scope.provide/use, manual Scope.make/close/fork, and how Layer.effect owns scopes in v4. - Advanced lifetime patterns: Covers ScopedRef for rotating resources, forkScoped/forkIn for fibers bound to scopes, child scopes for per-job lifetimes, and LIFO finalizer ordering semantics. - Use Case: When a database connection leaks in a long-running Effect service, apply this Skill to wrap acquisition in Effect.scoped at the right boundary or move it into a Layer.effect constructor with proper teardown. ## Quick Start Use the effect-scope skill to fix this Effect v4 code so the database connection is released when the request finishes.