This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from 'effect'. Also covers Effect + Next.js integration with @prb/effect-next.
Expert guidance for functional programming with the Effect library, covering error handling, dependency injection, composability, and testing patterns.
Before starting any Effect-related work, verify the Effect-TS source code exists at ~/.effect.
If missing, stop immediately and inform the user. Clone it before proceeding:
git clone https://github.com/Effect-TS/effect.git ~/.effect
Effect-TS has many ways to accomplish the same task. Proactively research best practices using the Task tool to spawn research agents when working with Effect patterns, especially for moderate to high complexity tasks.
Codebase Patterns First — Examine similar patterns in the current project before implementing. If Effect patterns exist in the codebase, follow them for consistency. If no patterns exist, skip this step.
Effect Source Code — For complex type errors, unclear behavior, or implementation details, examine the Effect
source at ~/.effect/packages/effect/src/. This contains the core Effect logic and modules.
HIGH Priority (Always Research):
MEDIUM Priority (Research if Complex):