Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.
Installs just this skill. Get the whole plugin for auto-invocation.
โก How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/cloudflare-workers-migration
๐๏ธ Context preview
The summary Claude sees to decide when to auto-load this skill.
Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.
๐ Stats
Stars194
Forks29
LanguageTypeScript
LicenseMIT
๐ฆ Ships with claude-skills
</> SKILL.md
cloudflare-workers-migration.SKILL.md
---name: cloudflare-workers-migration
description: Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.
metadata:
version: "1.0.0"
license: MIT
---# Workers Migration Guide
Migrate existing applications to Cloudflare Workers from various platforms.
## Migration Decision Tree
```
What are you migrating from?
โโโ AWS Lambda
โ โโโ Node.js handler? โ Lambda adapter pattern
โ โโโ Python? โ Consider Python Workers
โ โโโ Container/custom runtime? โ May need rewrite
โโโ Vercel/Next.js
โ โโโ API routes? โ Minimal changes with adapter
โ โโโ Full Next.js app? โ Use OpenNext adapter
โ โโโ Middleware? โ Direct Workers equivalent
โโโ Express/Node.js
โ โโโ Simple API? โ Hono (similar API)
โ โโโ Complex middleware? โ Gradual migration
โ โโโ Heavy node: usage? โ Compatibility layer
โโโ Other Edge (Deno Deploy, Fastly)
โโโ Standard Web APIs? โ Minimal changes
โโโ Platform-specific? โ Targeted rewrites