effect-patterns-streams-getting-started
Provides curated patterns for implementing lazy, memory-efficient streams in Effect-TS applications.
Install
mkdir -p .claude/skills/effect-patterns-streams-getting-started && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7484" && unzip -o skill.zip -d .claude/skills/effect-patterns-streams-getting-started && rm skill.zipInstalls to .claude/skills/effect-patterns-streams-getting-started
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Effect-TS patterns for Streams Getting Started. Use when working with streams getting started in Effect-TS applications.Key capabilities
- →Create lazy streams from iterables or values
- →Transform and filter data streams
- →Convert between Effect and Stream types
- →Consume streams using runCollect, runForEach, or runFold
- →Control stream size with take and drop operators
How it works
It utilizes Effect-TS Stream patterns to process data lazily, element-by-element, avoiding memory-intensive eager array operations.
Inputs & outputs
When to use effect-patterns-streams-getting-started
- →Migrating array operations to streams
- →Handling asynchronous data flows
- →Optimizing memory usage for large data sets
About this skill
Effect-TS Patterns: Streams Getting Started
This skill provides 4 curated Effect-TS patterns for streams getting started. Use this skill when working on tasks related to:
- streams getting started
- Best practices in Effect-TS applications
- Real-world patterns and solutions
🟢 Beginner Patterns
Your First Stream
Rule: Use Stream to process sequences of data lazily and efficiently.
Good Example:
import { Effect, Stream } from "effect"
// Create a stream from explicit values
const numbers = Stream.make(1, 2, 3, 4, 5)
// Create a stream from an array
const fromArray = Stream.fromIterable([10, 20, 30])
// Create a single-value stream
const single = Stream.succeed("hello")
// Transform and run the stream
const program = numbers.pipe(
Stream.map((n) => n * 2), // Double each number
Stream.filter((n) => n > 4), // Keep only > 4
Stream.runCollect // Collect results
)
Effect.runPromise(program).then((chunk) => {
console.log([...chunk]) // [6, 8, 10]
})
Anti-Pattern:
Don't use regular arrays when you need lazy processing or async operations:
// Anti-pattern: Eager processing, all in memory
const numbers = [1, 2, 3, 4, 5]
const doubled = numbers.map((n) => n * 2)
const filtered = doubled.filter((n) => n > 4)
This loads everything into memory immediately. Use Stream when:
- Data is large or potentially infinite
- Data arrives asynchronously
- You need backpressure or resource management
Rationale:
A Stream is a lazy sequence of values that can be processed one at a time. Create streams with Stream.make, Stream.fromIterable, or Stream.succeed.
Streams are Effect's answer to processing sequences of data. Unlike arrays which hold all values in memory at once, streams produce values on demand. This makes them ideal for:
- Large datasets - Process millions of records without loading everything into memory
- Async data - Handle data that arrives over time (files, APIs, events)
- Composable pipelines - Chain transformations that work element by element
Stream vs Effect - When to Use Which
Rule: Use Effect for single values, Stream for sequences of values.
Good Example:
import { Effect, Stream } from "effect"
// ============================================
// EFFECT: Single result operations
// ============================================
// Fetch one user - returns Effect<User>
const fetchUser = (id: string) =>
Effect.tryPromise(() =>
fetch(`/api/users/${id}`).then((r) => r.json())
)
// Read entire config - returns Effect<Config>
const loadConfig = Effect.tryPromise(() =>
fetch("/config.json").then((r) => r.json())
)
// ============================================
// STREAM: Multiple values operations
// ============================================
// Process file line by line - returns Stream<string>
const fileLines = Stream.fromIterable([
"line 1",
"line 2",
"line 3",
])
// Generate events over time - returns Stream<Event>
const events = Stream.make(
{ type: "click", x: 10 },
{ type: "click", x: 20 },
{ type: "scroll", y: 100 },
)
// ============================================
// CONVERTING BETWEEN THEM
// ============================================
// Effect → Stream (single value becomes 1-element stream)
const effectToStream = Stream.fromEffect(fetchUser("123"))
// Stream → Effect (collect all values into array)
const streamToEffect = Stream.runCollect(fileLines)
// Stream → Effect (process each value for side effects)
const processAll = fileLines.pipe(
Stream.runForEach((line) => Effect.log(`Processing: ${line}`))
)
// ============================================
// DECISION GUIDE
// ============================================
// Use Effect when:
// - Fetching a single resource
// - Computing a single result
// - Performing one action
// Use Stream when:
// - Reading files line by line
// - Processing paginated API results
// - Handling real-time events
// - Processing large datasets
// - Building data pipelines
Rationale:
Use Effect when your operation produces a single result. Use Stream when your operation produces multiple values over time.
Both Effect and Stream are lazy and composable, but they serve different purposes:
| Aspect | Effect | Stream |
|---|---|---|
| Produces | One value | Zero or more values |
| Memory | Holds one result | Processes incrementally |
| Use case | API call, DB query | File lines, events, batches |
Running and Collecting Stream Results
Rule: Choose the right Stream.run* method based on what you need from the results.
Good Example:
import { Effect, Stream, Option } from "effect"
const numbers = Stream.make(1, 2, 3, 4, 5)
// ============================================
// runCollect - Get all results as a Chunk
// ============================================
const collectAll = numbers.pipe(
Stream.map((n) => n * 10),
Stream.runCollect
)
Effect.runPromise(collectAll).then((chunk) => {
console.log([...chunk]) // [10, 20, 30, 40, 50]
})
// ============================================
// runForEach - Process each item
// ============================================
const processEach = numbers.pipe(
Stream.runForEach((n) =>
Effect.log(`Processing: ${n}`)
)
)
Effect.runPromise(processEach)
// Logs: Processing: 1, Processing: 2, etc.
// ============================================
// runDrain - Run for side effects only
// ============================================
const withSideEffects = numbers.pipe(
Stream.tap((n) => Effect.log(`Saw: ${n}`)),
Stream.runDrain // Discard values, just run
)
// ============================================
// runHead - Get first value only
// ============================================
const getFirst = numbers.pipe(
Stream.runHead
)
Effect.runPromise(getFirst).then((option) => {
if (Option.isSome(option)) {
console.log(`First: ${option.value}`) // First: 1
}
})
// ============================================
// runLast - Get last value only
// ============================================
const getLast = numbers.pipe(
Stream.runLast
)
Effect.runPromise(getLast).then((option) => {
if (Option.isSome(option)) {
console.log(`Last: ${option.value}`) // Last: 5
}
})
// ============================================
// runFold - Accumulate into single result
// ============================================
const sum = numbers.pipe(
Stream.runFold(0, (acc, n) => acc + n)
)
Effect.runPromise(sum).then((total) => {
console.log(`Sum: ${total}`) // Sum: 15
})
// ============================================
// runCount - Count elements
// ============================================
const count = numbers.pipe(Stream.runCount)
Effect.runPromise(count).then((n) => {
console.log(`Count: ${n}`) // Count: 5
})
Rationale:
Streams are lazy - nothing happens until you run them. Choose your run method based on what you need: all results, per-item effects, or just completion.
Effect provides several ways to consume a stream, each optimized for different use cases:
| Method | Returns | Use When |
|---|---|---|
| runCollect | Chunk<A> | Need all results in memory |
| runForEach | void | Process each item for side effects |
| runDrain | void | Run for side effects, ignore values |
| runHead | Option<A> | Only need first value |
| runLast | Option<A> | Only need last value |
| runFold | S | Accumulate into single result |
Take and Drop Stream Elements
Rule: Use take/drop to control stream size, takeWhile/dropWhile for conditional limits.
Good Example:
import { Effect, Stream } from "effect"
const numbers = Stream.make(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
// ============================================
// take - Get first N elements
// ============================================
const firstThree = numbers.pipe(
Stream.take(3),
Stream.runCollect
)
Effect.runPromise(firstThree).then((chunk) => {
console.log([...chunk]) // [1, 2, 3]
})
// ============================================
// drop - Skip first N elements
// ============================================
const skipThree = numbers.pipe(
Stream.drop(3),
Stream.runCollect
)
Effect.runPromise(skipThree).then((chunk) => {
console.log([...chunk]) // [4, 5, 6, 7, 8, 9, 10]
})
// ============================================
// Combine for pagination (skip + limit)
// ============================================
const page2 = numbers.pipe(
Stream.drop(3), // Skip first page
Stream.take(3), // Take second page
Stream.runCollect
)
Effect.runPromise(page2).then((chunk) => {
console.log([...chunk]) // [4, 5, 6]
})
// ============================================
// takeWhile - Take while condition is true
// ============================================
const untilFive = numbers.pipe(
Stream.takeWhile((n) => n < 5),
Stream.runCollect
)
Effect.runPromise(untilFive).then((chunk) => {
console.log([...chunk]) // [1, 2, 3, 4]
})
// ============================================
// dropWhile - Skip while condition is true
// ============================================
const afterFive = numbers.pipe(
Stream.dropWhile((n) => n < 5),
Stream.runCollect
)
Effect.runPromise(afterFive).then((chunk) => {
console.log([...chunk]) // [5, 6, 7, 8, 9, 10]
})
// ============================================
// takeUntil - Take until condition becomes true
// ============================================
const untilSix = numbers.pipe(
Stream.takeUntil((n) => n === 6),
Stream.runCollect
)
Effect.runPromise(untilSix).then((chunk) => {
console.log([...chunk]) // [1, 2, 3, 4, 5, 6]
})
// ============================================
// Practical: Process file with header
// ============================================
con
---
*Content truncated.*
When not to use it
- →Using arrays for large or infinite datasets
- →Performing eager processing for async data
Limitations
- →Requires understanding of Effect-TS ecosystem
- →Streams must be explicitly run to execute
How it compares
It focuses on lazy stream processing patterns for memory efficiency compared to standard eager array manipulation.
Compared to similar skills
effect-patterns-streams-getting-started side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| effect-patterns-streams-getting-started (this skill) | 1 | 7mo | No flags | Intermediate |
| turborepo | 61 | 2mo | Review | Intermediate |
| codex-skill | 12 | 5mo | Review | Advanced |
| run-nx-generator | 5 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by PaulJPhilp
View all by PaulJPhilp →You might also like
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
zod-4
prowler-cloud
Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.
copilot-sdk
github
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.
effect-ts-expert
ojowwalker77
This skill should be used when the user is working with Effect-TS, asks to "write Effect code", "use Effect", "functional TypeScript", "handle errors with Effect", "dependency injection Effect", "Effect Layer", or needs expert-level guidance on Effect-TS patterns, error handling, concurrency, and best practices.