brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
fp-errorsStop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code
Independent GitHub snapshot · Automated classification · Original documentation governs
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:
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.
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.
Either or TaskEither.