Menu
Publish a vibe-stack app live, read its public URL, view logs, and roll back. Use when the owner says deploy / publish / go live / roll back / veröffentlichen / online stellen / rückgängig.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Add per-person staff logins to a vibe-stack app's website using Cloudflare Access — the agent sets it up ITSELF via the Cloudflare API (works on the free workers.dev URL, no domain). Use only when SEVERAL people each need their OWN login (their own email); a single owner is already private via the access key. Triggers: "mein Team soll sich einloggen", "Mitarbeiter-Logins", "jeder mit eigener E-Mail", "staff logins".
Turn on AI inside a vibe-stack app's server so the WEBSITE (and autonomous tasks) can summarise, translate, or parse free text into saved data — using Cloudflare Workers AI, no API key and no extra account. Use when the owner wants the app itself to be "smart": "fass das zusammen", "übersetze", "erkenne automatisch", "aus dem Text rausziehen", "ich tippe einfach 'handvoll Erdbeeren mit Skyr' und es trägt sich ein", a free-text field that fills in fields by itself, or an AI step in a server task.
Manage Cloudflare resources for a vibe-stack app via wrangler — create the D1 database, create an R2 storage bucket, add a secret/API key, query D1 from the CLI, and regenerate types after editing wrangler.jsonc. Use when the owner mentions database, storage, bucket, secret, api key, binding, Cloudflare, Datenbank, or Speicher.
Connect a vibe-stack app to Claude as a custom connector so the owner can use it from anywhere — phone, desktop/web Chat, Projects, and routines, not just the Code tab. Provisions the OAUTH_KV namespace and the OWNER_SECRET access key, deploys, walks the owner (in German) through adding the custom connector, and generates the claude-setup/ paste bundle. Use when the owner wants to use/manage the app from their phone or outside the Code tab, "von überall", "auf dem Handy", "mit Claude verbinden", "Connector einrichten", or right after the first deploy.
RARELY needed — vibe-stack is ONE growing app, so a new thing is normally a new page (use add-page / add-data), NOT a new app. Only scaffold a fully separate app (its own DB + R2 + URL) when the owner explicitly insists on an isolated environment — confirm they don't just mean a new feature first. Then clone the kit, copy the boilerplate to ~/vibe-apps/<name>, rename, npm install, connect Cloudflare, deploy. Triggers: "wirklich eine eigene, getrennte App", "komplett separate app", "neu anfangen".
Set up a vibe-stack app as a BUSINESS / operations tool the owner runs by talking — define the things they manage (reservations, employees, orders, inventory, …) and the rules, then wire the data, a domain operating-manual, and a plain-language guide so the agent can run the live data. Use when the owner wants to manage a business, a team, bookings, or a shop (not just track personal data), e.g. "ich will Reservierungen und Mitarbeiter verwalten", "für mein Restaurant", "meinen Betrieb organisieren".
| name | vibe-deploy |
| description | Publish a vibe-stack app live, read its public URL, view logs, and roll back. Use when the owner says deploy / publish / go live / roll back / veröffentlichen / online stellen / rückgängig. |
Publish a vibe-stack app, hand the owner its live URL, view logs when something misbehaves, and roll back safely. Works for ANY vibe-stack app the owner has built.
The owner says any of: "veröffentlichen", "online stellen", "deploy", "go live", "die Änderung soll live gehen" — or for undo: "rückgängig machen", "zurück", "roll back".
npm run deploy does (one command, everything in sync)The starter's deploy script (in package.json) is:
npm run deploy → validate (format + types + build + tests) + wrangler d1 migrations apply DB --remote + wrangler deploy
So a single command first checks everything (npm run validate: Biome, type-check, build, and the
tests) — if any check fails, nothing is published, so a broken app can't go live — then applies
pending database migrations to the LIVE database (keeping the live data structure in sync with the
code) and publishes. You never apply remote migrations by hand — deploy does it. Run it from the
project folder.
If validate fails, read the cause, fix it, run npm run fix + npm run validate until green, then
deploy. Tell the owner in one calm German sentence that you found and fixed something first.
Say what you're about to do, in one German sentence:
"Ich veröffentliche deine Änderung jetzt — das dauert einen Moment."
Run it from the project root:
npm run deploy
When it succeeds, Wrangler prints the public URL in this shape:
https://<app-name>.<subdomain>.workers.dev
Read that exact line from the output and give the URL to the owner. Celebrate + reassure:
"🎉 Deine Änderung ist live! Hier ist deine App: " "Keine Sorge, ich kann jederzeit zurückrollen, falls dir etwas nicht gefällt."
On a phone they can open the browser menu and tap "Zum Home-Bildschirm" so it feels like a real app — mention it once:
"Tipp: Auf dem Handy kannst du im Browser-Menü 'Zum Home-Bildschirm' tippen — dann fühlt sich deine App wie eine echte App an."
Very first deploy only: on a brand-new account Wrangler may ask in the terminal to register a
free workers.dev subdomain (answer yes), and the new URL can be unreachable (a "523") for up
to a minute. Reassure, in German: "Beim allerersten Mal kann die Adresse eine knappe Minute
brauchen, bis sie reagiert — das ist ganz normal, einfach kurz warten."
The owner says "rückgängig" / "roll back". Reassure first, then run it:
"Kein Problem — ich mache die letzte Veröffentlichung rückgängig."
wrangler rollback
Then confirm:
"✅ Erledigt — die vorherige Version ist wieder live."
When the owner reports the live app acting up, watch the live request logs to see the real cause:
wrangler tail
This streams the Worker's live logs. Read them yourself, find the cause, and translate it into ONE
calm German sentence + the next single step. Never paste raw log output to the owner. (Logs are also
visible in the Cloudflare dashboard, since observability is enabled in wrangler.jsonc.) Stop the
stream with Ctrl+C when done.
If npm run deploy (or any wrangler command) fails with an authentication / "not logged in" /
"You are not authenticated" error, the owner's Cloudflare login expired. Re-run the login — it opens
their browser and only they can approve it:
npx wrangler login
Tell the owner, in German:
"Deine Cloudflare-Anmeldung ist abgelaufen. Es öffnet sich gleich dein Browser — melde dich an und klicke auf 'Allow', dann veröffentliche ich automatisch weiter."
After they approve, re-run npm run deploy.
~/vibe-apps/<app-name>).npm run dev server running for the owner — the live URL from npm run deploy is
the real thing.