Does this require a specific library?

The skill is designed to work with the @jagreehal/workflow library for composition, but the core Result pattern can be applied to any TypeScript project.

How does this skill handle third-party libraries that still throw errors?

It utilizes a step.try() utility that wraps throwing code (like JSON.parse or external SDKs) and maps those exceptions into typed Result objects for consistent processing.

What is the benefit of using Result types over throwing exceptions?

Result types make error cases explicit in the function signature, forcing developers to handle them at compile-time and preventing 'invisible' runtime crashes caused by unhandled exceptions.

What is railway-oriented programming in this context?

It is a pattern where functions are linked together like tracks; if one step returns an error, the execution 'switches tracks' to the error path and skips subsequent steps automatically.

Functional Result Types

Name: Functional Result Types
Author: jagreehal

byjagreehal

API開発

Implements explicit error handling and workflow composition using Result types to replace hidden exceptions in TypeScript.

概要

This skill guides Claude to adopt a functional approach to error handling by returning Result types instead of throwing exceptions. By making failure modes part of the function signature, it ensures that errors are visible, type-safe, and handled exhaustively. It leverages the @jagreehal/workflow library for railway-oriented programming, allowing complex business logic to be composed into clean, readable steps that automatically handle error propagation and short-circuiting.

主な機能

0 GitHub stars
Replaces invisible exceptions with explicit Result<T, E> types
Provides step.try() for bridging throwing third-party code into result pipelines
Standardizes mapping between domain errors and HTTP status codes
Integrates railway-oriented programming using createWorkflow
Enforces exhaustive error handling via TypeScript discriminated unions

ユースケース

Standardizing error responses across a REST or GraphQL API boundary
Composing multi-step business logic that requires clean short-circuiting on failure
Building mission-critical backend services where failure modes must be explicitly documented

概要

主な機能

0 GitHub stars
Replaces invisible exceptions with explicit Result<T, E> types
Provides step.try() for bridging throwing third-party code into result pipelines
Standardizes mapping between domain errors and HTTP status codes
Integrates railway-oriented programming using createWorkflow
Enforces exhaustive error handling via TypeScript discriminated unions

ユースケース

Standardizing error responses across a REST or GraphQL API boundary
Composing multi-step business logic that requires clean short-circuiting on failure
Building mission-critical backend services where failure modes must be explicitly documented