Scaffold and deploy Cloudflare Workers projects with Hono routing, Vite dev server, and Static Assets.
Works with
Guides you through project setup in four steps: understanding requirements, scaffolding structure, configuring bindings (D1, R2, KV), and deploying to production
Provides ready-to-use asset files including wrangler.jsonc , vite.config.ts , Hono app entry point, and TypeScript configuration
Documents critical patterns for export syntax, SPA fallback with API route protection, Vite pl
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncloudflare-worker-builderExecute the skills CLI command in your project's root directory to begin installation:
Fetches cloudflare-worker-builder from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cloudflare-worker-builder. Access via /cloudflare-worker-builder in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
697
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
697
stars
Scaffold a working Cloudflare Worker project from a brief description. Produces a deployable project with Hono routing, Vite dev server, and Static Assets.
Ask about the project to choose the right bindings and structure:
A brief like "todo app with database" is enough to proceed.
npm create cloudflare@latest my-worker -- --type hello-world --ts --git --deploy false --framework none
cd my-worker
npm install hono
npm install -D @cloudflare/vite-plugin vite
Copy and customise the asset files from this skill's assets/ directory:
wrangler.jsonc — Worker configurationvite.config.ts — Vite + Cloudflare pluginsrc/index.ts — Hono app with Static Assets fallbackpackage.json — Scripts and dependenciestsconfig.json — TypeScript configpublic/index.html — SPA entry pointAdd bindings to wrangler.jsonc based on project needs. Wrangler 4.45+ auto-provisions resources on first deploy — always specify explicit names:
{
"name": "my-worker",
"main": "src/index.ts",
"compatibility_date": "2025-11-11",
"assets": {
"directory": "./public/",
"binding": "ASSETS",
"not_found_handling": "single-page-application",
"run_worker_first": ["/api/*"]
},
// Add as needed:
"d1_databases": [{ "binding": "DB", "database_name": "my-app-db" }],
"r2_buckets": [{ "binding": "STORAGE", "bucket_name": "my-app-files" }],
"kv_namespaces": [{ "binding": "CACHE", "title": "my-app-cache" }]
}
npm run dev # Local dev at http://localhost:8787
wrangler deploy # Production deploy
// CORRECT — use this pattern
export default app
// WRONG — causes "Cannot read properties of undefined"
export default { fetch: app.fetch }
Source: honojs/hono #3955
Without run_worker_first, SPA fallback intercepts API routes and returns index.html instead of JSON:
"assets": {
"not_found_handling": "single-page-application",
"run_worker_first": ["/api/*"] // CRITICAL
}
Source: workers-sdk #8879
import { defineConfig } from 'vite'
import { cloudflare } from '@cloudflare/vite-plugin'
export default defineConfig({ plugins: [cloudflare()] })
Always set the main field in wrangler.jsonc — the Vite plugin needs it.
When adding cron triggers, switch to explicit export:
export default {
fetch: app.fetch,
scheduled: async (event, env, ctx) => { /* ... */ }
}
Read these for detailed troubleshooting:
references/common-issues.md — 10 documented issues with sources and fixesreferences/architecture.md — Route priority, caching, Workers RPCreferences/deployment.md — CI/CD, auto-provisioning, gradual rolloutsPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
Useful defaults in cloudflare-worker-builder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
cloudflare-worker-builder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend cloudflare-worker-builder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: cloudflare-worker-builder is focused, and the summary matches what you get after install.
Keeps context tight: cloudflare-worker-builder is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added cloudflare-worker-builder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
cloudflare-worker-builder reduced setup friction for our internal harness; good balance of opinion and flexibility.
cloudflare-worker-builder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
cloudflare-worker-builder has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: cloudflare-worker-builder is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 49