What is dependency injection in Effect?

Dependency injection in Effect is a pattern for managing requirements using Context (to define what a service is) and Layers (to define how a service is constructed), ensuring type-safety and modularity.

Can I use this skill to mock services for testing?

Yes, it provides patterns for creating in-memory or mock implementations of services and swapping them into the dependency graph using Layer.provide or Effect.provideService.

What are Scoped Layers in Effect?

Scoped Layers are used for services that require lifecycle management, such as opening and closing database connections or file handles, using finalizers for guaranteed cleanup.

How do I define a service with this skill?

Services are defined using Context.GenericTag to create a unique identifier for an interface, which can then be implemented by various Layers.

Effect Dependency Injection

Name: Effect Dependency Injection
Author: TheBushidoCollective

byTheBushidoCollective

•

API Development

Manages complex dependency graphs and service lifecycles in Effect-based TypeScript applications using type-safe Context and Layers.

About

This skill empowers Claude to architect robust, testable TypeScript applications by mastering the Effect library's dependency injection system. It provides comprehensive patterns for defining service interfaces with type-safe Tags, constructing modular Layers for service implementations, and composing sophisticated dependency graphs using pipelines and merging. From managing database connections with automatic cleanup via scoped layers to implementing the repository and facade patterns for clean architecture, this skill ensures scalable and maintainable dependency management throughout the application lifecycle.

Key Features

Type-safe service definitions using Context and GenericTag
72 GitHub stars
Automatic resource management and finalizers for service cleanup
Modular layer construction with succeed, effect, and scoped variants
Advanced dependency composition using layer merging and pipelines
Streamlined testing patterns through mock and in-memory layer overrides

Use Cases

Architecting large-scale TypeScript backends using clean architecture principles
Configuring multi-environment applications with environment-specific service layers
Decoupling business logic from infrastructure using the Repository and Facade patterns

About

Key Features

Type-safe service definitions using Context and GenericTag
72 GitHub stars
Automatic resource management and finalizers for service cleanup
Modular layer construction with succeed, effect, and scoped variants
Advanced dependency composition using layer merging and pipelines
Streamlined testing patterns through mock and in-memory layer overrides

Use Cases

Architecting large-scale TypeScript backends using clean architecture principles
Configuring multi-environment applications with environment-specific service layers
Decoupling business logic from infrastructure using the Repository and Facade patterns