Guide Effect usage in TypeScript and Bun code for I/O and runtime boundaries.
npx skills add https://github.com/darkmatter/skills --skill effect-typescript
Please help me install this Agent Skill. Skill: effect-typescript Source: https://github.com/darkmatter/skills/tree/main/skills/effect-typescript Command: npx skills add https://github.com/darkmatter/skills --skill effect-typescript
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.
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.
High-intent search queries and answers about installing and using this skill.
Use Effect for TypeScript workflows involving meaningful I/O, typed failures, dependencies, validation, retries, resources, or long-lived runtime boundaries. Plain async code remains suitable for small one-off scripts and pure functions.
Build database-backed services using Effect Layers to establish typed dependency injection and safe resource lifecycles. This approach ensures validated boundaries, deterministic tests, and Bun-compatible tooling conventions for production deployments.
Effect works with Bun commands and Alchemy-based deployment workflows by applying typed dependency injection, bounded retries, and safe resource lifecycles. This integration supports deployable infrastructure with typed errors and Effect-aware testing.
The best way to handle typed errors and retries in TypeScript is using Effect's runtime boundaries. Effect provides typed error management, bounded retries, and scoped resources to ensure safe resource lifecycles within your services.
Validate runtime boundaries using Effect Schema to enforce type-safe data validation in TypeScript. Schema integrates with Effect services and Config to provide deterministic tests and typed dependency injection across your application.
Effect is recommended for queue workers, scheduled jobs, and API clients because they involve meaningful I/O and typed failures. Plain TypeScript is better reserved for small one-off scripts and pure functions without complex dependencies.
PaulJPhilpStandardize cross-platform Effect-TS operations for file I/O and environment access.
darkmatterConfigure and troubleshoot Alchemy v2 infrastructure for TypeScript and Effect applications.
TitoPrauseeConfigure Effect-TS test layers with SQLite-backed mocks for deterministic service testing.
thktIdentify testability gaps in TypeScript/React codebases.
