sitekit ships as a single self-contained executable plus its bundled pack assets. This is the recipient guide — you were handed a binary and want to install it, point an AI agent at it, and start building.
You don’t need to memorize commands. After install, you drive sitekit by talking to your agent. The steps below are what happens under the hood — but in practice you install once and let the agent run the CLI.

​
Install the binary

macOS or Linux, with curl and tar (both preinstalled on every Mac and most Linux boxes). One command: 
curl -fsSL https://github.com/yevgetman/sitekit-dist/releases/latest/download/install.sh | sh
sitekit --version
The installer detects your OS and CPU, downloads the matching build, installs to ~/.local/share/sitekit/, symlinks ~/.local/bin/sitekit, clears the macOS Gatekeeper quarantine flag, and smoke-tests sitekit --version. Supported platforms: macOS (Apple Silicon + Intel) and Linux (arm64 + x64).
~/.local/bin isn’t on your PATH. Add this line to ~/.zshrc (or ~/.bashrc), then reopen your shell:
export PATH="$HOME/.local/bin:$PATH"
The binary is unsigned and Gatekeeper quarantined it. The curl installer strips the quarantine automatically; if you extracted a tarball by hand, run:
xattr -d com.apple.quarantine ./sitekit
There’s no native Windows build. Install WSL2 (a Linux environment for Windows) and run the same command from your WSL shell — it installs the Linux build.

​
Install the agent skill

sitekit is built to be driven by an LLM coding agent. After installing the CLI, install the bundled skill into your harness so the agent knows how to use it: Installing the skill also co-installs two design helpers as siblings (frontend-design and open-ui-component-catalog). Opt out with --no-design-skill / --no-component-catalog. Re-run with --force to refresh after an upgrade. See The agent skill for what it contains and how the agent uses it.

​
What gets installed, and where

PathWhat
~/.local/share/sitekit/sitekitthe binary (~60 MB — embeds the runtime + sitekit)
~/.local/share/sitekit/assets/bundled voice / style / shape / skill packs the binary reads at runtime
~/.local/bin/sitekitsymlink on your PATH
~/.claude/skills/sitekit/the agent skill (only after init-skill)
The binary reads packs from assets/, which must stay next to the binary — the installer keeps them together, so you don’t manage this yourself. Nothing else on your system is touched.

​
Expiry — time-limited builds

A shared sitekit binary is time-limited. You get 30 days from your own first run, and every build also has a hard backstop (90 days from when it was built) — whichever comes first.
After the window passes, every command exits with E_SITEKIT_BUILD_EXPIRED. The window starts the first time you run it (tracked in ~/.config/sitekit/.runtime.json); the backstop date is printed in the README.md inside the tarball. Rolling your system clock back won’t extend it. To renew: ask whoever shared it to cut a fresh build, then re-run the install one-liner — it always pulls the newest release and resets your window.

​
Updating

Re-run the installer. It’s idempotent and clean-replaces the binary + assets with the latest release: 
curl -fsSL https://github.com/yevgetman/sitekit-dist/releases/latest/download/install.sh | sh
Your machine-local packs (~/.sitekit/), saved playbooks (~/.config/sitekit/), and the installed agent skill are untouched by an update. After updating, refresh the skill with sitekit init-skill --target claude-code --force.

​
Uninstall

curl -fsSL https://github.com/yevgetman/sitekit-dist/releases/latest/download/uninstall.sh | sh
This removes the binary, assets/, and the symlink. It deliberately leaves your user data in place — your workshop packs (~/.sitekit/), saved playbooks (~/.config/sitekit/), and the agent skill (~/.claude/skills/sitekit/). Delete those by hand for a fully clean slate.

​
Manual install (no curl, or offline)

If you were sent a tarball directly: 
# Download the tarball for your platform from:
#   https://github.com/yevgetman/sitekit-dist/releases/latest
tar xzf sitekit-darwin-arm64.tar.gz
./sitekit-darwin-arm64/sitekit --version
Platform tarballs: sitekit-darwin-arm64 (Apple Silicon), sitekit-darwin-x64 (Intel Mac), sitekit-linux-x64, sitekit-linux-arm64. To put it on your PATH, move both the binary and its assets/ dir together (they must stay siblings): 
sudo mv sitekit-darwin-arm64/sitekit  /usr/local/bin/sitekit
sudo mv sitekit-darwin-arm64/assets   /usr/local/bin/assets
sitekit --version

​
What you need for deploy and media

Everything core works with the binary alone. A few capabilities reach for outside tools:
CapabilityNeeds
Deploy to Cloudflare PagesA Cloudflare account + wrangler login once. Wrangler itself is fetched on demand via npx — no global install.
Visual QA (verify --visual)Playwright, not bundled in the binary. Install separately: npm install -g playwright && npx playwright install chromium. The rest of verify works without it.
Image generation / vision (sitekit media)OPENAI_API_KEY (default image + vision provider) or ANTHROPIC_API_KEY (alternative vision provider), set in your environment.
Payments / email (Tier B/C)Stripe + Resend accounts and API keys, set via sitekit secrets set — never hardcoded.

​
Troubleshooting

The assets/ directory got separated from the binary. Re-run the installer, or move assets/ back next to the binary.
The release URL isn’t resolving. Confirm https://github.com/yevgetman/sitekit-dist/releases/latest opens in a browser; if not, the share link may be wrong or the release was removed.
Your install window (or the build’s hard backstop) has passed. Ask for a fresh build and re-run the installer — see Expiry.

​
What’s next

Build your first site

The end-to-end first run, driven by your agent.

The agent skill

What init-skill installs and how the agent uses it.