setup

name	setup
description	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.
disable-model-invocation	true
allowed-tools	Read, Edit, Write, Bash(uname:*), Bash(hugo:*), Bash(git --version), Bash(command -v:*), Bash(git rev-parse:*), Bash(git init:*), Bash(git add:*), Bash(git commit:*), Bash(bash scripts/dev-hugo.sh:*), mcp__Claude_Preview__preview_start, mcp__Claude_Browser__preview_start

Set up your site

Take a freshly downloaded copy of the kit from nothing to a running preview, and leave the owner looking at a site they can see, ready for their first instruction. The owner may be setting up a development environment for the first time, so keep it friendly and plain, and say what each step is for.

Homebrew is the owner's to install, since it needs their admin password: hand over the one-line installer and have them run it in their own Terminal. Installing the tools with it, brew install hugo git, is yours to run. Everything else, the checks, version control, and the preview, is yours too.

Take stock

As your first step, run these to see what's already here:

uname -s
hugo version
git --version
command -v brew
git rev-parse --is-inside-work-tree

Read what they show before acting. A command that prints an error like "command not found" means that tool isn't installed — that's expected here, not a problem to stop on.

• Hugo must be installed. The extended edition (its version line includes the word extended) is recommended — it lets the image pipeline output smaller WebP images — but isn't required; without it, images fall back to their original format and the build still succeeds.
• Git is needed for saving the owner's work and, later, publishing it.
• Homebrew is the recommended installer on macOS (command -v brew prints a path if it's there, nothing if not).
• A git repo already? git rev-parse --is-inside-work-tree prints true if saving is already set up: a "Use this template" clone is a repo; a downloaded ZIP is not.

1. Install what's missing

If Hugo or Git is missing, get them installed. On macOS, Homebrew is the simplest path.

• If Homebrew itself is missing, point the owner to the one-line installer at brew.sh. It asks for their password, so they run it in their own Terminal.
• With Homebrew present, install the tools yourself:

  brew install hugo git
  

  Homebrew's Hugo is the extended edition, which gives the smaller WebP images.

Then re-run the stock check to confirm both tools are present. On Windows or Linux there's no Homebrew, so point the owner to Hugo's installation guide (the extended edition is recommended for WebP) and Git's downloads, which they install themselves.

2. Set up saving

If the project isn't a git repo yet, initialize one so the owner has an undo history from the first moment:

git init
git add -A
git commit -m "Initial commit"

That first commit is the base state: the point "undo" can return to, and what the starter kit is diffed against. Do it quietly; there's no need to teach Git. If the project is already a repo (a template clone), leave its history alone and skip this.

3. Start the preview

Get the owner looking at their running site. Which path depends on where this session runs:

• Desktop or web app: the in-app preview pane is available (labeled Preview in older versions, Browser in newer ones). Start it with preview_start, selecting the Preview site (Hugo server) config (from .claude/launch.json), so the site opens in a pane beside the chat instead of a background process the owner has to go find.
• Terminal: no panel exists, so run the dev server in the background and share the address it prints:

  bash scripts/dev-hugo.sh
  

  It usually serves at http://localhost:1313.

Either way, confirm the site actually comes up. If the build fails, fix it before going on; the owner should land on a working site, not an error.

4. Hand off

Tell the owner the site is running, where to see it (the preview pane beside the chat, or the address it's serving on in a terminal), and what they can do next, then stop and let them steer:

Your site is running. Take a look at the preview, then tell me what you'd like to change.

Notes

• Nothing here is public or destructive, so there's no confirmation step, and /setup is safe to run again anytime; it reads the environment rather than leaving a marker.
• Homebrew is the owner's to install; the tools are yours. Installing Homebrew needs an admin password, so that step is the owner's, run in their own Terminal. brew install hugo git needs none, so you run it. On Windows or Linux the owner runs the OS installers themselves.