Effect

Use this skill to write Effect code that reads like normal TypeScript where business logic matters, while still using Effect's composition model for errors, observability, retries, layers, and dependency wiring.

First Steps

1. Inspect the project before editing:
   • Check package.json for effect, @effect/*, TypeScript settings, test scripts, and lint/typecheck commands.
   • Search existing code for Effect.gen, pipe, Layer, Context.Tag, Data.TaggedError, and catchTag.
   • Match the repo's import style and Effect version. Do not introduce a second style casually.
2. If the task is nontrivial, read Gen vs Pipe Patterns before changing code.
3. Prefer a small typed Effect boundary over rewriting an entire module. Keep normal synchronous pure helpers as plain functions unless Effect adds real value.

Style Rule

Use Effect.gen for business logic and .pipe(...) for composition.