Puts the site on the internet for the first time. Connects it to GitHub and sets up an automatic build-and-deploy pipeline on Cloudflare Workers (recommended, for a custom domain) or GitHub Pages (the fast on-ramp when you don't have a domain yet). Use when the owner is ready to go live, or wants to launch, deploy, or get the site online for the first time. One-time setup, separate from /publish, which sends later updates.
Gets a freshly downloaded copy of the kit running. Checks for the tools the site needs, helps install anything missing, initializes version control, and starts the preview. Use right after downloading the kit, when the owner says "set up" or "get started", or when the preview won't run.
Resets the site to a true blank canvas so the owner can start fresh: deletes the demo pages (About, blog, onboarding guides), blanks the home page, strips the layout back to bare content, and neutralizes the site's identity and launch marker. The engine, styles, config, and .claude context stay, and a recovery checkpoint is saved first so nothing is lost. Use when the owner wants to start over, clear the demo, wipe the example content, or reset the site to nothing.
Sends the owner's latest changes to the live site. Use for everyday updates once the site is online, whenever the owner wants to publish, go live, or push changes to the web. Not first-time setup; that's /launch.
Safely moves the site to a newer version of Hugo, the tool that builds it. It checks the current pin against the latest stable, reviews what changed, and only with the owner's OK bumps the pin, installs the matching Hugo, and rebuilds to confirm nothing broke. Use when the owner wants to update or upgrade Hugo, asks whether there's a newer version, or a deploy failed because the pinned Hugo is out of date. Occasional maintenance, separate from everyday /publish.