Effect Seam Migration
Move heavy or long-running work off a constrained runtime (for example the Cloudflare Workers memory or CPU ceiling) by first extracting domain logic into packages as Effect programs, then moving execution. Use when starting or continuing a runtime migration or moving a service across app boundaries.
Install
npx skills add jpoehnelt/skills --skill effect-seam-migrationgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/effect-seam-migration ~/.claude/skills/effect-seam-migrationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Effect-seam runtime migration Separate extraction from the runtime move so each step preserves behavior. Never register unextracted app code on a new runtime. Use `effect` for runners and layers. Assumes Effect v4. Repo facts (from AGENTS.md): where packages live, the runtimes and their entrypoints, any workflow ownership catalog or manifest assertion, shared event contracts, Effect gates, and check, test, and local-run commands. ## Extract (finish first) 1. Identify the workload: entry point, callers, dependencies, resource lifetime. Record implicit authorization, tenant scoping, ordering, deduplication, retry identity, and error behavior. 2. Move app-independent logic into an owning package. Pure synchronous logic stays outside Effect; I/O is exposed as Effect programs with service dependencies in `R`. Packages never import an app. 3. Move the unit's tests into the package. Only route, transport, and runtime-boundary integration tests stay beside the app. 4. Keep execution on the existing runtime until focused checks and the existing integration path pass. Keep the repo's Effect gates (round-trip, thin-wrapper, runtime-exit checks) green. ## Move (after extraction) 1. Compose the required layers at the destination entry point and run programs only through its boundary runner. 2. Establish exactly one execution owner. If the repo has an ownership catalog or manifest, add the unit there and register it on the new runtime in the same change.
Details
- Skill name
effect-seam-migration- Repository
- jpoehnelt/skills
- Path
effect-seam-migration/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Effect Seam Migration skill do?
Move heavy or long-running work off a constrained runtime (for example the Cloudflare Workers memory or CPU ceiling) by first extracting domain logic into packages as Effect programs, then moving execution. Use when starting or continuing a runtime migration or moving a service across app boundaries.
How do I install the Effect Seam Migration skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill effect-seam-migration. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Effect Seam Migration popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Gcd
9rochacbruno/gcd-claude-skill
Google Cloud Dedicated (GCD) and Cloud de Confiance (S3NS) sovereign cloud expert. Use when working with sovereign Google Cloud regions, or when the user mentions GCD, Google Cloud Dedicated, Cloud de Confiance, S3NS, sovereign cloud, universe domain, apis-berlin-build0.goog, s3nsapis.fr, u-germany-northeast1, u-france-east1, Trusted Partner Cloud, TPC, or data sovereignty requirements for Google Cloud workloads. Provides guidance on region-specific services, authentication, Terraform, networking, and key differences from public Google Cloud. Also use when asked to review a PR, code review, or
Alchemy Infra
23jpoehnelt/skills
Change, plan, deploy, or debug infrastructure declared with Alchemy (v2) and secrets from Infisical. Use for alchemy stack edits, bindings, Durable Object classes, D1 or other migrations, custom domains, local Docker stacks, adding or rotating a Worker secret, secret drift between Infisical, CI, and the Worker, deploy failures, or rollback.
Liveblocks Best Practices
9liveblocks/skills
Use this skill when building, debugging, or answering questions about Liveblocks. Liveblocks gives you the building blocks and infrastructure to enable people and AI to work together inside your app, powering realtime collaboration.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.