Install

Set up cubek on this machine: install the CLI with `curl -fsSL https://cubek.dev/install | sh`, and bun (https://bun.sh) if it is missing.
Save the output of `cubek skill` as your cubek Skill and add the MCP server (Claude Code: `claude mcp add cubek -- cubek mcp`).
Run `cubek --help` to confirm, then tell me what you set up.

Your agent can do all of this from the prompt above. By hand: cubek is one CLI. It compiles your app locally, runs it with cubek dev, and deploys it. You need:

• The cubek CLI: one binary for macOS (Apple Silicon and Intel, macOS 11+) and Linux (x86_64 and arm64, glibc 2.28+); on Windows, use WSL. The script checks the release signature (or its SHA-256 where openssl cannot, as with macOS's LibreSSL) and installs it in ~/.local/bin, or /usr/local/bin when that is writable and ~/.local/bin is not on your PATH (CUBEK_INSTALL_DIR to change it, CUBEK_VERSION to pin a version); it prints the line to add to your shell's profile when needed (~/.zprofile for macOS's zsh). The macOS binaries are not notarized yet: installed with the script they run as is; a copy downloaded with a browser is quarantined by Gatekeeper (xattr -d com.apple.quarantine ./cubek lifts it). The CLI keeps itself up to date (checked in the background; cubek upgrade updates now; CUBEK_NO_UPDATE=1 turns it off and only warns when it is behind).
• bun on the machine that deploys: it bundles browser code and runs cubek test.

curl -fsSL https://cubek.dev/install | sh
curl -fsSL https://bun.sh/install | bash
cubek --help

The Skill is a single page (about 4K tokens) that teaches a coding agent the whole platform. For Claude Code:

mkdir -p ~/.claude/skills/cubek
cubek skill > ~/.claude/skills/cubek/SKILL.md

For Cursor, save it as a project rule (.cursor/rules/cubek.mdc); for Codex and others, append it to the project's AGENTS.md.

The MCP server exposes the CLI as tools (check, deploy, logs, SQL...) plus sdk_types, the exact API as .d.ts:

claude mcp add cubek -- cubek mcp