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.

Cette compétence doit être utilisée lorsque l'utilisateur pose des questions sur "Effect services", "injection de dépendances", "Effect.Tag", "Context.Tag", "Layer", "Effect.provide", "Effect.provideService", "implémentation de service", "gestion des dépendances", "Layer.succeed", "Layer.effect", "Layer.scoped", "composer des couches", "Layer.merge", "Layer.provide", "services par défaut", « mémorisation des couches », « testabilité », « couches de test », « services simulés » ou doit comprendre comment Effect gère le paramètre de type Exigences (R). Source : andrueandersoncs/claude-skill-effect-ts.

Voir l'original