Skip to content

jezweb/claude-skills / archive/plugins/cloudflare/skills/cloudflare-worker-builder

cloudflare-worker-builder

Verified

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

assets/public/index.html

View on GitHub
<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Cloudflare Worker + Hono + Static Assets</title>
	<link rel="stylesheet" href="/styles.css">
</head>
<body>
	<div class="container">
		<header>
			<h1>🔥 Cloudflare Worker + Hono + Static Assets</h1>
			<p>Testing API routes with Workers Static Assets and SPA fallback</p>
		</header>

		<section class="test-section">
			<h2>API Tests</h2>
			<p>These API routes are handled by the Worker thanks to <code>run_worker_first</code> configuration.</p>

			<div class="test-group">
				<button onclick="testHello()">Test /api/hello</button>
				<button onclick="testData()">Test /api/data</button>
				<button onclick="testEcho()">Test /api/echo (POST)</button>
				<button onclick="testHealth()">Test /api/health</button>
			</div>

			<div id="results">
				<h3>Results:</h3>
				<pre id="output">Click a button to test the API...</pre>
			</div>
		</section>

		<section class="info-section">
			<h2>✅ What This Demonstrates</h2>
			<ul>
				<li><strong>Static Assets</strong>: This HTML is served from <code>public/</code></li>
				<li><strong>API Routes</strong>: <code>/api/*</code> routes are handled by Worker first</li>
				<li><strong>SPA Fallback</strong>: Unknown routes return this index.html</li>
				<li><strong>Hono Framework</strong>: Type-safe routing with JSON responses</li>
				<li><strong>ES Module Format</strong>: Correct export pattern prevents build errors</li>
			</ul>
		</section>

		<footer>
			<p>
				📚 <a href="https://developers.cloudflare.com/workers/static-assets/">Static Assets Docs</a> |
				<a href="https://hono.dev/docs/getting-started/cloudflare-workers">Hono Docs</a> |
				<a href="https://developers.cloudflare.com/workers/vite-plugin/">Vite Plugin Docs</a>
			</p>
		</footer>
	</div>

	<script src="/script.js"></script>
</body>
</html>
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall