Notes on versioning the whole vibe
Essays, deep dives, and tutorials on building software when the prompt is the source — and the vb CLI versions every bit of it.
The vibe is the new commit
Git versions the code. But the code is no longer the source of truth — the prompt, the spec, and the model that produced it are. Here is why we are versioning the whole vibe.
Mara Lindqvist
May 20, 2026 · 6 min read
Latest articles
5 posts
Deep DiveInside the vibe object: spec, prompts, diff, and eval in one bundle
A vibe is more than a commit with extra metadata. We break down the four-part structure of the vibe object and how vb stores it alongside your git history.
Devon Pryce
May 12, 2026 · 8 min read
WorkflowForking a vibe: remixing AI-built software
Forking a repo gives you the code. Forking a vibe gives you the code, the prompts, the spec, and the config — so you can change the intent and regenerate, not just patch the output.
Ada Okonkwo
May 4, 2026 · 5 min read
Engineeringvb replay: making AI builds reproducible
Non-determinism is the dirty secret of AI-assisted development. vb replay pins the model, config, and seed so a vibe rebuilds the same way today, next quarter, and on someone else’s machine.
Devon Pryce
Apr 22, 2026 · 7 min read
CollaborationPrompt diffs: code review for the AI era
Reviewing 800 lines of generated code is the wrong job. Reviewing the three sentences that generated them is the right one. How vb diff puts prompts and specs into the review.
Ada Okonkwo
Apr 10, 2026 · 6 min read
TutorialFrom prompt to published vibe: a full walkthrough
A start-to-finish tour: initialize a repo with vb, build a feature with an agent, capture the vibe, and publish it to VibeHub so anyone can fork and replay it.
Ren Takahashi
Mar 28, 2026 · 9 min read