cloudflare-worker-builder
Scaffold and deploy Cloudflare Workers projects with Hono routing, Vite dev server, and Static Assets.
Works with
1
total installs
1
this week
697
GitHub stars
0
upvotes
Install Skill
Run in your terminal
1
installs
1
this week
697
stars
What it does
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
Installation Guide
How to use cloudflare-worker-builder on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
cloudflare-worker-builder
Run the install command
Execute 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.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
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.
Security Notice
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.
Documentation
Cloudflare Worker Builder
Scaffold a working Cloudflare Worker project from a brief description. Produces a deployable project with Hono routing, Vite dev server, and Static Assets.
Workflow
Step 1: Understand the Project
Ask about the project to choose the right bindings and structure:
- What does the app do? (API only, SPA + API, landing page)
- What data storage? (D1 database, R2 files, KV cache, none)
- Auth needed? (Clerk, better-auth, none)
- Custom domain or workers.dev subdomain?
A brief like "todo app with database" is enough to proceed.
Step 2: Scaffold the Project
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 point
Step 3: Configure Bindings
Add 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" }]
}
Step 4: Deploy
npm run dev # Local dev at http://localhost:8787
wrangler deploy # Production deploy
Critical Patterns
Export Syntax
// CORRECT — use this pattern
export default app
// WRONG — causes "Cannot read properties of undefined"
export default { fetch: app.fetch }
Source: honojs/hono #3955
Static Assets + API Routes
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
Vite Config
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.
Scheduled/Cron Handlers
When adding cron triggers, switch to explicit export:
export default {
fetch: app.fetch,
scheduled: async (event, env, ctx) => { /* ... */ }
}
Reference Files
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 rollouts
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ 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.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
wordpress-elementor
84jezweb/claude-skills
react-native
20jezweb/claude-skills
zustand-state-management
7jezweb/claude-skills
onboarding-ux
4jezweb/claude-skills
dependency-audit
4jezweb/claude-skills
vitest
3jezweb/claude-skills
Reviews
- GGanesh Mohane★★★★★Dec 16, 2024
Useful defaults in cloudflare-worker-builder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- YYuki Choi★★★★★Dec 16, 2024
cloudflare-worker-builder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- SSakura Khanna★★★★★Dec 4, 2024
I recommend cloudflare-worker-builder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMeera Wang★★★★★Dec 4, 2024
Solid pick for teams standardizing on skills: cloudflare-worker-builder is focused, and the summary matches what you get after install.
- LLuis Ghosh★★★★★Nov 23, 2024
Keeps context tight: cloudflare-worker-builder is the kind of skill you can hand to a new teammate without a long onboarding doc.
- MMia Khanna★★★★★Nov 23, 2024
We added cloudflare-worker-builder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- SSakura Wang★★★★★Nov 15, 2024
cloudflare-worker-builder reduced setup friction for our internal harness; good balance of opinion and flexibility.
- SSakshi Patil★★★★★Nov 7, 2024
cloudflare-worker-builder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAva Robinson★★★★★Nov 7, 2024
cloudflare-worker-builder has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CChaitanya Patil★★★★★Oct 26, 2024
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
Discussion
Comments — not star reviews- No comments yet — start the thread.