effect-errors-retries
Errors & Retries
When to use
- You’re defining domain errors and recovery policies
- You need to map infrastructure errors to domain boundaries
- You must add retries, backoff, jitter, and timeouts
Model Errors
import { Data } from "effect"
class ValidationError extends Data.TaggedError("ValidationError")<{ field: string; reason: string }>{}
class NotFoundError extends Data.TaggedError("NotFoundError")<{ id: string }>{}
Map/Boundary
const repoCall = Effect.fail(new ValidationError({ field: "name", reason: "empty" }))
More from mepuka/effect-ontology
effect-index
Skill index and decision guide. Use to pick the right Effect Skill quickly and follow a minimal decision tree.
314effect-patterns-hub
Complete catalog of 130+ Effect-TS patterns from EffectPatterns repository. Use when looking for specific implementation patterns, best practices, or real-world examples. Complements other skills with concrete, curated patterns.
38effect-concurrency-fibers
Concurrency with Effect.all, forEach concurrency, Fiber lifecycle, race and timeouts. Use for parallelizing tasks safely.
28effect-testing-mocking
Testing patterns with layers, mocks, and deterministic time. Use when preparing testable services and small smoke tests.
26effect-queues-background
Queue and PubSub patterns, background fibers, and graceful shutdown. Use for decoupling producers/consumers.
26effect-foundations
Core Effect foundations and style for a coding agent. Use when starting an Effect task, choosing operators, or structuring a small pipeline.
22