effect-patterns-concurrency-getting-started
Effect-TS patterns for Concurrency Getting Started. Use when working with concurrency getting started in Effect-TS applications.
Install
mkdir -p .claude/skills/effect-patterns-concurrency-getting-started && curl -L -o skill.zip "https://mcp.directory/api/skills/download/4939" && unzip -o skill.zip -d .claude/skills/effect-patterns-concurrency-getting-started && rm skill.zipInstalls to .claude/skills/effect-patterns-concurrency-getting-started
About this skill
Effect-TS Patterns: Concurrency Getting Started
This skill provides 3 curated Effect-TS patterns for concurrency getting started. Use this skill when working on tasks related to:
- concurrency getting started
- Best practices in Effect-TS applications
- Real-world patterns and solutions
π’ Beginner Patterns
Race Effects and Handle Timeouts
Rule: Use Effect.race for fastest-wins, Effect.timeout for time limits.
Good Example:
import { Effect, Option } from "effect"
// ============================================
// BASIC RACE: First one wins
// ============================================
const server1 = Effect.gen(function* () {
yield* Effect.sleep("100 millis")
return "Response from server 1"
})
const server2 = Effect.gen(function* () {
yield* Effect.sleep("50 millis")
return "Response from server 2"
})
const raceServers = Effect.race(server1, server2)
Effect.runPromise(raceServers).then((result) => {
console.log(result) // "Response from server 2" (faster)
})
// ============================================
// BASIC TIMEOUT: Limit execution time
// ============================================
const slowOperation = Effect.gen(function* () {
yield* Effect.sleep("5 seconds")
return "Finally done"
})
// Returns Option.none if timeout
const withTimeout = slowOperation.pipe(
Effect.timeout("1 second")
)
Effect.runPromise(withTimeout).then((result) => {
if (Option.isNone(result)) {
console.log("Operation timed out")
} else {
console.log(`Got: ${result.value}`)
}
})
// ============================================
// TIMEOUT WITH FALLBACK
// ============================================
const withFallback = slowOperation.pipe(
Effect.timeoutTo({
duration: "1 second",
onTimeout: () => Effect.succeed("Using cached value"),
})
)
Effect.runPromise(withFallback).then((result) => {
console.log(result) // "Using cached value"
})
// ============================================
// TIMEOUT FAIL: Throw error on timeout
// ============================================
class TimeoutError {
readonly _tag = "TimeoutError"
}
const failOnTimeout = slowOperation.pipe(
Effect.timeoutFail({
duration: "1 second",
onTimeout: () => new TimeoutError(),
})
)
// ============================================
// RACE ALL: Multiple competing effects
// ============================================
const fetchFromCache = Effect.gen(function* () {
yield* Effect.sleep("10 millis")
return { source: "cache", data: "cached data" }
})
const fetchFromDB = Effect.gen(function* () {
yield* Effect.sleep("100 millis")
return { source: "db", data: "fresh data" }
})
const fetchFromAPI = Effect.gen(function* () {
yield* Effect.sleep("200 millis")
return { source: "api", data: "api data" }
})
const raceAll = Effect.raceAll([fetchFromCache, fetchFromDB, fetchFromAPI])
Effect.runPromise(raceAll).then((result) => {
console.log(`Winner: ${result.source}`) // "cache"
})
// ============================================
// PRACTICAL: API with timeout and fallback
// ============================================
const fetchWithResilience = (url: string) =>
Effect.gen(function* () {
const response = yield* Effect.tryPromise(() =>
fetch(url).then((r) => r.json())
).pipe(
Effect.timeout("3 seconds"),
Effect.flatMap((opt) =>
Option.isSome(opt)
? Effect.succeed(opt.value)
: Effect.succeed({ error: "timeout", cached: true })
)
)
return response
})
Rationale:
Use Effect.race when you want the first result from competing effects. Use Effect.timeout to limit how long an effect can run.
Racing and timeouts prevent your app from hanging:
- Redundant requests - Race multiple servers, use fastest response
- Timeouts - Fail fast if operation takes too long
- Fallbacks - Try fast path, fall back to slow path
Understanding Fibers
Rule: Fibers are lightweight threads managed by Effect, enabling efficient concurrency without OS thread overhead.
Good Example:
import { Effect, Fiber } from "effect"
// ============================================
// WHAT IS A FIBER?
// ============================================
// A fiber is a running effect. When you run an effect,
// it executes on a fiber.
const myEffect = Effect.gen(function* () {
yield* Effect.log("Hello from a fiber!")
yield* Effect.sleep("100 millis")
return 42
})
// This runs myEffect on the "main" fiber
Effect.runPromise(myEffect)
// ============================================
// FORKING: Create a new fiber
// ============================================
const withFork = Effect.gen(function* () {
yield* Effect.log("Main fiber starting")
// Fork creates a new fiber that runs independently
const fiber = yield* Effect.fork(
Effect.gen(function* () {
yield* Effect.log("Child fiber running")
yield* Effect.sleep("200 millis")
yield* Effect.log("Child fiber done")
return "child result"
})
)
yield* Effect.log("Main fiber continues immediately")
yield* Effect.sleep("100 millis")
yield* Effect.log("Main fiber waiting for child...")
// Wait for the forked fiber to complete
const result = yield* Fiber.join(fiber)
yield* Effect.log(`Got result: ${result}`)
})
Effect.runPromise(withFork)
/*
Output:
Main fiber starting
Child fiber running
Main fiber continues immediately
Main fiber waiting for child...
Child fiber done
Got result: child result
*/
// ============================================
// FIBER OPERATIONS
// ============================================
const fiberOps = Effect.gen(function* () {
const fiber = yield* Effect.fork(
Effect.gen(function* () {
yield* Effect.sleep("1 second")
return "done"
})
)
// Check if fiber is done (non-blocking)
const poll = yield* Fiber.poll(fiber)
yield* Effect.log(`Poll result: ${poll}`) // None (still running)
// Wait for completion
const result = yield* Fiber.join(fiber)
yield* Effect.log(`Join result: ${result}`)
// Or interrupt if taking too long
// yield* Fiber.interrupt(fiber)
})
Rationale:
Fibers are Effect's lightweight threads. They're cheap to create (thousands are fine), automatically managed, and can be interrupted cleanly.
Unlike OS threads:
- Lightweight - Create thousands without performance issues
- Cooperative - Yield control at effect boundaries
- Interruptible - Can be cancelled cleanly
- Structured - Parent fibers manage children
Your First Parallel Operation
Rule: Use Effect.all with concurrency option to run independent effects in parallel.
Good Example:
import { Effect } from "effect"
// Simulate async operations
const fetchUser = Effect.gen(function* () {
yield* Effect.sleep("100 millis")
return { id: 1, name: "Alice" }
})
const fetchProducts = Effect.gen(function* () {
yield* Effect.sleep("150 millis")
return [{ id: 1, name: "Widget" }, { id: 2, name: "Gadget" }]
})
const fetchCart = Effect.gen(function* () {
yield* Effect.sleep("80 millis")
return { items: 3, total: 99.99 }
})
// ============================================
// SEQUENTIAL: One after another (~330ms)
// ============================================
const sequential = Effect.all([fetchUser, fetchProducts, fetchCart])
// ============================================
// PARALLEL: All at once (~150ms)
// ============================================
const parallel = Effect.all(
[fetchUser, fetchProducts, fetchCart],
{ concurrency: "unbounded" }
)
// ============================================
// PARALLEL WITH LIMIT: Max 2 at a time
// ============================================
const limited = Effect.all(
[fetchUser, fetchProducts, fetchCart],
{ concurrency: 2 }
)
// ============================================
// DEMO
// ============================================
const demo = Effect.gen(function* () {
const start = Date.now()
const [user, products, cart] = yield* parallel
const elapsed = Date.now() - start
yield* Effect.log(`Fetched in ${elapsed}ms`)
yield* Effect.log(`User: ${user.name}`)
yield* Effect.log(`Products: ${products.length}`)
yield* Effect.log(`Cart total: $${cart.total}`)
})
Effect.runPromise(demo)
// Output: Fetched in ~150ms (not ~330ms!)
Rationale:
Use Effect.all with { concurrency: "unbounded" } to run independent effects in parallel. Without the option, effects run sequentially.
Parallel execution speeds up independent operations:
- Fetch multiple APIs - Get user, products, cart simultaneously
- Process files - Read multiple files at once
- Database queries - Run independent queries in parallel
More by PaulJPhilp
View all skills by PaulJPhilp βYou might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversMCP Installer simplifies dynamic installation and configuration of additional MCP servers. Get started easily with MCP I
Securely join MySQL databases with Read MySQL for read-only query access and in-depth data analysis.
Context Portal: Manage project memory with a database-backed system for decisions, tracking, and semantic search via a k
Dot AI (Kubernetes Deployment) streamlines and automates Kubernetes deployment with intelligent guidance and vector sear
Claude Historian is a free AI search engine offering advanced search, file context, and solution discovery in Claude Cod
Claude Historian: AI-powered search for Claude Code conversationsβfind files, errors, context, and sessions via JSONL pa
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.