effect-patterns-error-handling

Model error patterns in Effect-TS applications with tagged errors and recovery strategies.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/scotttrinh/nook --skill effect-patterns-error-handling-scotttrinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-patterns-error-handling
Source: https://github.com/scotttrinh/nook/tree/main/.agents/skills/effect-patterns-error-handling
Command: npx skills add https://github.com/scotttrinh/nook --skill effect-patterns-error-handling-scotttrinh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured patterns to manage errors in Effect-TS applications, enabling safer composition, clearer context, and reliable recovery strategies.

Core Features & Use Cases

  • Error propagation and context: maintain rich error data across layered calls.
  • Error pattern catalog: previews of accumulating errors, chained recovery, and custom error types.
  • Recovery strategies: per-error-type handling, retry, fallback, and user-friendly messages for robust resilience.

Quick Start

Load a minimal example to understand how tagged errors are caught and recovered in an Effect-TS program.

Frequently Asked Questions about effect-patterns-error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle errors in Effect-TS without losing context across layered calls?

Effect-TS error handling allows you to maintain rich error data across layered calls by using tagged errors and contextual causes. This ensures structured error propagation and preserves domain semantics throughout your application layers.

What is the best way to implement retry and fallback strategies in TypeScript using Effect-TS?

Effect-TS provides structured recovery strategies for TypeScript applications, enabling per-error-type handling, retries, and fallbacks. You can apply chained recovery patterns to build robust resilience and translate errors into user-friendly messages.

How do tagged errors improve domain semantics in TypeScript applications?

Tagged errors improve domain semantics by allowing you to model specific error types explicitly in Effect-TS. This pattern supports per-error recovery strategies and helps maintain clear, structured error data across your application's layered architecture.

Can I accumulate multiple errors in Effect-TS instead of failing on the first exception?

Yes, Effect-TS supports accumulating errors through its error pattern catalog. This allows your TypeScript application to collect multiple failures simultaneously rather than short-circuiting, enabling comprehensive validation and structured error reporting.

Does Effect-TS error handling work for user-facing messages in TypeScript projects?

Yes, Effect-TS error handling supports translating domain-specific tagged errors into user-friendly messages. This allows your TypeScript application to maintain robust internal error semantics while displaying clear, contextual recovery messages to end users.

When should I use custom error types in Effect-TS?

Use custom error types in Effect-TS when you need to model domain-specific failures with rich context. This pattern enables per-error-type recovery strategies, ensuring structured propagation and targeted retry logic across layered application calls.