skills.rest
spencerbeggs
spencerbeggsCOMMUNITY
Explore all skills by this author →
GitHub

effect-v4-construct-map

Map Effect v3 constructs to their v4 idiomatic counterparts.

2|Updated Jul 2, 2026
Search Tags:#typescript#refactoring#api#schema#migration#effect
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-construct-map
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effect-v4-construct-map
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-v4-construct-map
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-construct-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the friction and uncertainty of migrating codebases from Effect v3 to v4 by providing a centralized, verified lookup for API renames, structural changes, and removed constructs.

Core Features & Use Cases

  • API Mapping: Instant lookup for v3-to-v4 construct renames, including Effect core, Schema, and SQL modules.
  • Behavioral Audits: Identifies silent breaking changes where code compiles but behaves differently, such as structural equality defaults.
  • Use Case: When porting a library, use this Skill to verify if a v3 construct like Effect.async or Schema.Literal has been removed or renamed, preventing runtime errors and ensuring idiomatic v4 implementation.

Quick Start

Consult the effect-v4-construct-map to identify the v4 equivalent for the Effect.async construct and verify its usage against the provided migration tables.

Frequently Asked Questions about effect-v4-construct-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Effect v3 constructs to v4?▼

To find v4 equivalents for removed constructs like Effect.async or Schema.Literal, use an API mapping reference that verifies construct renames and checks usage against migration tables. This prevents runtime errors when porting libraries.

What are the breaking changes when upgrading Effect schema and core modules?▼

To find v4 equivalents for removed constructs like Effect.async or Schema.Literal, use an API mapping reference that verifies construct renames and checks usage against migration tables. This prevents runtime errors when porting libraries.

Does my Effect v3 to v4 migration require manual schema refactoring?▼

To find v4 equivalents for removed constructs like Effect.async or Schema.Literal, use an API mapping reference that verifies construct renames and checks usage against migration tables. This prevents runtime errors when porting libraries.

What is the best way to audit Effect TypeScript code for silent v4 breaking changes?▼

To find v4 equivalents for removed constructs like Effect.async or Schema.Literal, use an API mapping reference that verifies construct renames and checks usage against migration tables. This prevents runtime errors when porting libraries.

Why does my Effect v4 code compile but behave differently after migration?▼

To find v4 equivalents for removed constructs like Effect.async or Schema.Literal, use an API mapping reference that verifies construct renames and checks usage against migration tables. This prevents runtime errors when porting libraries.

Related Skills

Explore More Software Engineering Skills→
mpsuessermpsuesser
22

effect-schema-v4

Migrate Effect TypeScript Schema code from v3 to v4 patterns.

Community
Intermediate
MyHeavenDyfMyHeavenDyf

effect

Provide TypeScript code examples for Effect v4 typed services and workflows.

Community
Intermediate
jlcanelajlcanela
1

effect-v4-migration

Migrate TypeScript projects from Effect v3 to Effect v4 module layout.

Community
Intermediate
Razaib-khanRazaib-khan

fetching-library-docs

Fetch concise library API docs and examples via Context7 MCP.

Community
Advanced