Development and migration guidance for Effect v4, a beta programming framework with patterns for services, layers, generators, schemas, and error handling. It also explains how to upgrade Effect v3 code to v4.

Use it when building Effect v4 applications or migrating projects from v3, including work with services, layers, schema codecs, generators, and error handling.

It helps account for renamed APIs, behavior changes, and unstable beta modules when writing or upgrading Effect code. Older examples may no longer match the current beta.

effect-v4 — Skill by teeverc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/teeverc/effect-ts/effect-v4

Any agent

npx skills add teeverc/effect-ts --skill effect-v4

Clone the repo

git clone --depth 1 https://github.com/teeverc/effect-ts

Made for: Claude Code, Codex.

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,526 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00069	$0.02526
Opus 5	$0.00034	$0.01263
Sonnet 5	$0.00014	$0.00505
Haiku 4.5	$0.00007	$0.00253

Measured 2d ago against content hash c53d18870d67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

effect-v4 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/effect-v4/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Effect v4 (Beta) - Development & Migration

Overview

Comprehensive guidance for Effect v4 development and migration from v3. This skill provides:

v4 Core Patterns - Guide to building new v4 code with Context, layers, generators, schema codecs
v3 → v4 Migration - Step-by-step migration guidance with API renames, behavior changes, and before/after examples

Status: Effect v4 is beta software under active development in effect-smol. The core programming model is stable, but effect/unstable/* modules may receive breaking changes in minor releases. For production use, review official v4 beta guidance and stability notes.

All bundled migration guides are sourced from the official effect-smol migration documentation.

Upstream Changes Through June 30, 2026

The upstream beta changed substantially after the original February 22, 2026 baseline and again after the April 9, 2026 skill refresh. Treat older examples that mention ServiceMap, Schema.makeUnsafe, SchemaParser.makeUnsafe, or Effect.Yieldable as stale. Current guidance should prefer:

Context.Service / Context.Reference / Context<R> instead of ServiceMap.*
Schema.make(...) instead of Schema.makeUnsafe(...)
SchemaParser.make(...) instead of SchemaParser.makeUnsafe(...)
Schema.makeEffect(...) when constructor-style validation should fail in the error channel instead of throwing
Effectable.Class / Effectable.Prototype for custom Effect-like values; do not recommend Effect.Yieldable or .asEffect()
Schema.asserts(schema, input) / SchemaParser.asserts(schema, input), not generated assertion helpers

Quick Triage

Building v4 Code

Core Effect types and combinators (Result, Option, Chunk, Duration): references/core-usage.md
Broader data types (DateTime, BigDecimal, HashSet, Redacted): references/data-types-advanced.md
Equality, Order, Hash, Equivalence semantics: references/behavior-traits.md
Expected errors vs defects, catch* combinators: references/error-management.md
Sandboxing, Cause inspection, catchCause: references/error-tooling.md
Exit and Cause structure, result inspection: references/exit-cause.md
Services and dependency injection (Context, layers): references/dependency-management.md
Layer construction, memoization, { local: true }: references/layer-patterns.md
Resource lifecycles, Scope, acquireRelease: references/resource-management.md
Running effects, Runtime removal, run boundaries: references/runtime-execution.md
Fibers, forkChild, forkDetach, fork options: references/concurrency.md
References (replaces FiberRef), Context.Reference: references/concurrency-advanced.md
Schedules, repetition, spaced/fixed/exponential: references/scheduling.md
Retries, backoff, schedule composition: references/scheduling-retry.md
Streams, queues, PubSub, STM: references/streams-queues-stm.md
HTTP clients and external APIs: references/http-client.md
HTTP servers and API definitions: references/http-server.md
Request batching and data loaders: references/request-resolver.md
Caching and memoization: references/caching.md
Configuration and config providers: references/configuration.md
Advanced config, redaction: references/configuration-advanced.md
Logs, metrics, tracing: references/observability.md
Logger/metrics/tracing setups and exporters: references/observability-examples.md
Wiring log/metric/trace layers: references/observability-wiring.md
Sequential workflows and generator patterns: references/generators.md
Upstream research notes and post-April beta changes: references/upstream-changes-2026-06-30.md
Schema validation, parsing, encoding (codecs): references/schema.md
Stream consumption with reducers (Sink): references/sink.md
Deterministic time in tests (TestClock): references/testing.md
Broader testing services and test layers: references/testing-stack.md
Command, FileSystem, Path, Terminal, KeyValueStore: references/platform-primitives.md
LLM workflows, planning, tool use via Effect AI: references/ai.md
Bundle-size constrained runtimes (Micro): references/micro.md
Migrating from Promise/async: references/migration-async.md
Common pitfalls and runtime errors: references/troubleshooting.md
Docs-to-guide map from llms.txt: references/docs-index.md

Read the full file on GitHub · 167 lines

Files

What ships with it

50 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 167 lines · 69 tokens per session scan A c53d18870d67

Subscribe to this mod's changes

effect-v4 is a skill published in the GitHub repository teeverc/effect-ts (5 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 2,526 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens