vibe

---

vibe kit is two things that ship together but stand alone:

• The spec framework — a durable .spec/ planning layer (product / tech / design / plan / lessons) with templates and a validator. Works with any agent, or none.
• The vibe flow — a state-machine workflow for Claude Code that routes each phase (strategy / feature / quick) to the right skills and subagents, injects per-turn "orders", and guards its own write invariants with hooks.

All bash, Markdown, and JSON — no runtime, no build step. The repo builds itself with its own harness, so what you install is exactly what is dogfooded here.

Install

Prerequisites: bash and curl (or wget), plus git for the target repo. jq is recommended (scripts degrade gracefully without it). The claude CLI is needed only for the plugin / --global install.

One command

No clone required — run it straight from the web, from inside the repo you want vibe kit in:

curl -fsSL https://raw.githubusercontent.com/LennardZuendorf/vibe/main/install.sh | bash

It fetches a snapshot (override with VIBE_REF=<branch|tag>) and runs a local install into the current repo. Pass flags after bash -s -- (e.g. … | bash -s -- --dry-run). Or, from a clone:

git clone https://github.com/LennardZuendorf/vibe.git && cd vibe
./install.sh

Run it from inside the repo you want vibe kit in, or pass a target path. A bare run searches upward for the enclosing repo (a .spec/.git marker) and, on a terminal, asks which mode you want:

Mode	Command	What you get
local (default)	./install.sh <repo>	Full stateful vibe kit into that repo: the spec + vibe skills, the /flow command, and the four Claude Code hooks wired via .claude/settings.json. Self-contained — teammates get it through git.
global	./install.sh --global	The per-user plugin (vibe@vibe, user scope): only the portable, stateless surface — the spec + vibe skills and the doctrine hook — applied in every vibe kit repo. Needs the claude CLI.

./install.sh <repo>              # local: full vibe kit into <repo>
./install.sh --global            # per-user plugin (across all your repos)
./install.sh --with-plugins      # also install companion plugins (superpowers)
./install.sh <repo> --only spec  # spec framework only (any agent, or none)
./install.sh <repo> --only flow  # flow engine only (no spec skill)
./install.sh <repo> --adapters claude   # symlink CLAUDE.md -> AGENTS.md (opt-in, never clobbers)
./install.sh <repo> --dry-run    # preview; writes nothing

As a Claude Code plugin

The repo is its own marketplace, so you can install the per-user plugin directly:

claude plugin marketplace add LennardZuendorf/vibe
claude plugin install vibe@vibe

That is exactly what ./install.sh --global runs for you. The plugin ships the spec + vibe skills and a self-detecting SessionStart doctrine hook — not the stateful flow (/flow, cursor, guard hooks), which stays a local install.

What a local install does

Copies the platform-neutral core into <repo>/.agents/skills/, merges AGENTS.md inside managed markers (your prose is never touched), seeds and gitignores the flow cursor, and wires the four Claude hooks (SessionStart, UserPromptSubmit, PreToolUse, Stop) into .claude/settings.json. Re-running is idempotent and preserves a live cursor. No plugin to register — /flow is a native project command.

Companion tools

--with-plugins installs a companion set via the claude CLI at user scope — currently superpowers, with a feature-dev slot ready to fill in. It degrades gracefully when the CLI is absent. "caveman" is not a plugin: vibe kit injects a one-line caveman style brevity note into the doctrine each session.

Uninstall

Removes only what vibe kit installed and keeps your content (.spec/**, your AGENTS.md prose, and the flow cursor unless --yes):

# No clone, from inside the installed repo:
curl -fsSL https://raw.githubusercontent.com/LennardZuendorf/vibe/main/install.sh | bash -s -- --uninstall