From prompt to published vibe: a full walkthrough

This walkthrough takes a fresh repository all the way to a published, forkable vibe. You will need the vb CLI from the alpha — everything else is standard git.

1. Wrap your repo

vb init sets up the parallel vibe namespace next to your git history. Nothing about your existing repo changes.

vb init
  ✓ vibe namespace created
  ✓ git history untouched (12 commits)

2. Write the spec first

Describe what you want before you prompt for it. The spec is what reviewers read and what vb replay checks against later.

# spec.md
Add a /healthz endpoint that returns 200 and
the current git SHA as JSON. No auth.

3. Build with an agent

Drive your agent as usual. vb watches the session in the background and records the transcript, tool calls, and config — you do not change how you work.

4. Capture the vibe

vb commit bundles the diff with the spec, the transcript, and the eval into a single vibe object.

vb commit -m "add /healthz endpoint"
  ✓ diff captured (2 files)
  ✓ 1 spec, 14 prompts, 3 checks
  vibe 9b2e1a committed

5. Publish and share

vb push sends both your git commits and their vibes to VibeHub. The vibe gets a public page with an "Open in vb" button, so anyone can fork the intent and replay it on their own machine.

vb push
  ✓ pushed to origin (git)
  ✓ published 1 vibe to vibehub.co/you/your-repo

“You did not just ship code. You shipped the recipe for it.”