effect-typescript

What problem does it solve?

This Skill helps you decide when TypeScript code should use Effect instead of plain async code, especially when the work involves meaningful I/O, typed failures, dependencies, validation, retries, resources, or long-lived runtime boundaries.

Core Features & Use Cases

• Judgment for adoption: Distinguishes small one-off scripts and pure functions from workflows that benefit from Effect.
• Production patterns: Guides you through services, Layers, Schema validation, Config, retries, scoped resources, and testable boundaries.
• Darkmatter conventions: Adapts upstream Effect guidance to Bun commands and Alchemy-based deployment workflows.
• Use cases: Building API clients, database-backed services, queue workers, scheduled jobs, and deployable infrastructure with typed errors and deterministic tests.

Quick Start

Ask for an Effect-first review of your TypeScript task and have it recommend whether to use plain code or a Layer-based Effect design, with Bun and Alchemy conventions applied where relevant.