인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
개발 및 엔지니어링 · SKILL.md

fp-errors

fp-errors

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: fp-errors description: Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code risk: critical source: community date_added: "2026-09-04" version: 1.0.0 author: kadu tags:

  • fp-ts
  • error-handling
  • either
  • task-either
  • typescript
  • validation
  • practical

Practical Error Handling with fp-ts

This skill teaches you how to handle errors without try/catch spaghetti. No academic jargon - just practical patterns for real problems.

The core idea: Errors are just data. Instead of throwing them into the void and hoping someone catches them, return them as values that TypeScript can track.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

  • You need to replace exception-heavy code with Either or TaskEither.
  • The task involves validation, domain errors, or clearer error contracts in TypeScript.
  • You want pragmatic fp-ts error-handling guidance for real application code.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
저장한 Skills