requirements management

SKILL.md

The third type parameter in Effect represents requirements - services and dependencies the effect needs to run:

Effect uses a powerful dependency injection system based on Context and Layer.

The primary reason to define services is testability. Every external dependency (API calls, databases, file systems, third-party SDKs) MUST be wrapped in a Context.Tag service so that tests can provide a test implementation instead of hitting real systems. This is how Effect achieves 100% test coverage — business logic depends only on service interfaces, and tests swap in test layers that control all I/O.

Esta habilidad debe usarse cuando el usuario pregunta sobre "Servicios de efectos", "inyección de dependencia", "Effect.Tag", "Context.Tag", "Layer", "Effect.provide", "Effect.provideService", "implementación de servicios", "administración de dependencias", "Layer.succeed", "Layer.effect", "Layer.scoped", "componer capas", "Layer.merge", "Layer.provide", "default" servicios", "memorización de capas", "capacidad de prueba", "capas de prueba", "servicios simulados" o necesita comprender cómo Effect maneja el parámetro de tipo Requisitos (R). Fuente: andrueandersoncs/claude-skill-effect-ts.

Ver original