cloudflare

> **Plan mode**: If you are planning work, this entire skill is ONE plan step: "Invoke /vibes:cloudflare". Do not decompose the steps below into separate plan tasks. ``` ╔═══════════════════════════════════════════════╗ ║ ☁️ CLOUDFLARE WORKERS DEPLOY ║ ║ Deploy API · Pocket ID · Edge Functions ║ ╚═══════════════════════════════════════════════╝ ``` ## Deploy to Cloudflare Deploy your Vibes app to Cloudflare Workers via the Deploy API. ### Prerequisites 1. **Assembled HTML file** (from `/vibes:vibes` or `/vibes:sell`) 2. **Pocket ID account** (browser login on first deploy) No Cloudflare account or wrangler CLI needed — the Deploy API handles infrastructure. ### Quick Deploy ```bash VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}" bun "$VIBES_ROOT/scripts/deploy-cloudflare.js" --name myapp --file index.html ``` On first run, a browser window opens for Pocket ID authentication. Tokens are cached for subsequent deploys. **Static Assets:** Place images, fonts, or other static files in an `assets/` directory next to the app file. The deploy script auto-discovers and includes them (binary files are base64-encoded). Reference in code with absolute paths like `/assets/logo.png`. ### Deploy with AI enabled ```bash VIBES_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "${CLAUDE_SKILL_DIR}")")}" bun "$VIBES_ROOT/scripts/deploy-cloudflare.js" --name myapp --file index.html --ai-key "sk-or-v1-your-key" ``` The ...