Ship AI-built software without the vibe hangover

The release engine for AI-built software.
It mapped itself, fixed itself, packaged itself, and built its own distribution path.

Website · Quick Start · Docker · Manifesto · FAQ

---

The Weekend Hangover

We are AI-native. AI generates code, but it doesn't deliver it.

Most AI tools finish their job at the first draft. They leave you with a codebase that looks like it works, but falls apart when you try to ship it. You get hit with the Vibe Hangover:

• Auth held together with tape that kills your enterprise deals during technical reviews.
• God tables with 35 columns that cause timeouts and massive serverless bills.
• Silent failures where a crashed Stripe webhook loses 8% of your revenue and you never get an alert.
• Deploy and pray strategies that take down the app on a Friday afternoon.

(Read the full use case: The 4 ways AI-coded MVPs break in production)

---

The Promise

We ship AI-built software.

𝚅𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍. is not another code generator. It is the release engine you run after AI has produced a repo and before a real user touches it. It forces that repo through perception, verification, convergence, install truth, packaging, and launch-readiness checks until a stranger can install it, trust it, and actually use it.

---

The VetCoders Axioms

1. AI-Native, not AI-assisted: We don't write the code. We craft the delivery.
2. Perception over Memory: The agent must see the structural truth now, not rely on stale summaries.
3. Code Mapping over Green Quality Gates: Passing tests on broken architecture is just a faster train on the wrong tracks.
4. Intentions over RAG: Retrieve why we built it, not just a blind vector search of how.
5. Move On over Backward Compatibility: If the abstraction is rotting, cut it. Don't preserve garbage "just in case."

---

The Hero Loop

It's obvious AI will generate code. 𝚅𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍. asks: what is still wrong?

The system finds the problems, fixes them, and repeats the loop until nothing important is left.

1. The Draft: You build an MVP using Cursor, Copilot, or Claude. 2. The Finding: Quality gates and structural maps locate the exact failures. 3. The Fix: The agent eliminates the counterexamples. 4. The Close: We run the loop. We don't stop until P0 / P1 / P2 = 0.

---

The System Under The Hood

Behind this simple effect is an architecture built to orchestrate, map, and execute. (No longer guessing the architecture, but seeing it).

Layer	How it works
Seeing it All	The agent stops guessing architecture. It uses Loctree to see the entire project structure, dead code, and dependencies before it changes anything.
Convergence	vc-marbles runs the loop. It is not trying to "prove correctness." It only asks "what is still wrong?" and fixes it.
Multi-Agent	vc-agents lets you spin up Claude, Codex, and Gemini in parallel right in your terminal. Compare their results or have them tackle different architectural slices at the same time.
The Final Check	vc-dou (Definition of Undone) asks if it's shippable: Can you install it? Can someone trust it? Is there an onboarding page?

---

The Three Marks

𝚅𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍. has three typographic signatures — one for each layer of craft:

Mark	Layer	When to use
⚒🅅·🄸·🄱·🄴·🄲·🅡·🄰·🄵·🅃·🄴·🄳·	Produced with	Full product built through the framework
𝓥𝓲𝓫𝓮𝓬𝓻𝓪𝓯𝓽𝓮𝓭	Designed with	Design, UI, visual identity, brand work
//𝚟𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍.	Developed with	Source code, engineering, infrastructure

The `` is not decoration. It is the mark.

---

Install

Non-destructive. Interactive. Transparent. Reversible.

Prefer the guided browser path when you are onboarding a founder, PM, or less terminal-native operator:

curl -fsSL https://vibecrafted.io/install.sh | bash -s -- --gui

Both entrypoints use the same trust-first bootstrap: it explains what it will do and asks before proceeding on an attended terminal. Pass --yes when you want to pre-approve that bootstrap prompt.

The guided path stages the local control plane, bootstraps the foundation layer, runs the same compact installer truth used by automation, and leaves a readable START_HERE.md behind.

Use the direct compact path when you are scripting the install or you already know you want the terminal-only flow:

curl -fsSL https://vibecrafted.io/install.sh | bash

The bootstrap prints the snapshot source, staging location, and next installer step before it stages or installs anything on your machine.

Inside a local checkout, make vibecrafted opens the terminal-native installer wizard — the built-in vetcoders-installer runner driven from install.toml, with reason + consent per phase and cargo-style sticky progress. make install routes through the same runner with auto-approve, so automation and humans share one engine.

Shell is our everyday workforce entry and all the tools are terminal-native. Nevertheless if you need GUI we also offer it! Run make wizard to keep the same trust-building cadence directly in the browser.

Verify:

make -C $VIBECRAFTED_ROOT/.vibecrafted/tools/vibecrafted-current doctor

Prefer a containerized operator runtime when you want the framework isolated from the host toolchain:

docker build -t vetcoders/vibecrafted:local .
docker run --rm -it -v "$PWD:/workspace" vetcoders/vibecrafted:local version

See Docker Runtime.

---

Quick Start

cd $VIBECRAFTED_ROOT/your-project
vibecrafted init claude
vibecrafted implement codex --prompt "Add JWT authentication"

Existing vibecrafted justdo / vc-justdo calls remain compatibility aliases, but new docs and scripts should use implement.

Type vibecrafted help for the command deck, or vc- and hit tab once the shell helpers are installed.

When you want to walk the release surface explicitly, run:

vibecrafted dou claude --prompt "Audit launch readiness"
vibecrafted decorate codex --prompt "Polish the release surface"
vibecrafted hydrate codex --prompt "Package the product"
vibecrafted release codex --prompt "Prepare release steps"

vibecrafted release enforces a four-section release report — Semgrep security gate (make semgrep), exposed surface inventory, deployment mode decision, and post-release install smoke from the published artifact. The doctrine lives in skills/vc-release/SKILL.md and the canonical template lives in skills/vc-release/references/release-report-template.md.

---

For Founders

Free for personal use and for startups. No limits on repos or agents.

For enterprise: info@vibecrafted.io

---

Move fast, but with taste.
Finish the whole thing, not just the code.

//𝚟𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍.

_{(c)2024-2026 VetCoders · vibecrafted.io}