DOCUMENTATION
BACK TO MAIN FIG. 15 Β· DWG VC-015

The 14 documents that ship with vibecrafted.

Install path, architecture, vc-* skills reference, release discipline, FAQ. Sourced from the canonical repo at vetcoders/vibecrafted and synced to this site. No marketing prose: each document is the same one an operator reads at the terminal.

Install

How to put vibecrafted on a workstation and confirm the install is real.

  1. Docker Runtime

    The Docker image packages the Vibecrafted command deck as a portable operator runtime. Source lives at /opt/vibecrafted; the project under audit is mounted at /workspace; runtime state is written to…

    Open
  2. Installing πš…πš’πš‹πšŽπšŒπš›πšŠπšπšπšŽπš.

    Vibecrafted v1.x ships a native install path for macOS, Linux (Debian/Ubuntu/Arch/Fedora), and WSL2. Native Windows install is deferred to v2.x β€” see Windows below for the current bridge via WSL.

    Open
  3. iTerm2 Stack (GA since v1.8.0)

    Plan 10 (META_22) β€” promoted from [experimental] framing on 2026-05-12.

    Open
  4. Quick Start

    You have an AI-built repo. You want to ship it without the vibe hangover.

    Open
  5. Zellij Multi-Agent Layouts

    VibeCrafted ships a zellij configuration tuned for the way VetCoders actually work: parallel agents, shared Living Tree, mesh of workstations, no babysitting. The shipped surface gives every layout a…

    Open

Architecture

How the framework is shaped, why the seams sit where they do, and what each layer is allowed to know.

  1. Frontier Config β€” Starship, Atuin, Optional Zellij

    Frontier config is the lightweight operator layer that still belongs inside the current framework surface:

    Open
  2. Perception: How Agents See the Codebase

    Language models cannot guess architecture topology. And they should not pretend to.

    Open
  3. πš…πš’πš‹πšŽπšŒπš›πšŠπšπšπšŽπš. Foundation

    Foundation packages are infrastructure that all skills depend on. They are not skills β€” they are the senses and memory of the agent layer.

    Open
  4. Workflows

    This page documents how the command deck actually chains skills today. It is a runtime map of scripts/vibecrafted, the shared helper layer, and the skill contracts in skills/.

    Open

Skills reference

The vc-* skills β€” what each does, when to invoke it, and what truth it leaves behind.

  1. Contributing a New Vibecrafted Skill

    This guide walks an operator (human or agent) through authoring a new vc-* skill from scratch and getting it merged into vibecrafted.

    Open
  2. Skills

    This index documents the live framework inventory in skills/ and the routes currently exposed by scripts/vibecrafted.

    Open

Release

Release engineering and shipping discipline β€” turning "done in the repo" into "safe to deploy."

  1. Release Kickoff

    This is the pre-release operator sheet for πš…πš’πš‹πšŽπšŒπš›πšŠπšπšπšŽπš.

    Open

FAQ

Questions people ask before they trust the framework. Honest answers, not marketing.

  1. πš…πš’πš‹πšŽπšŒπš›πšŠπšπšπšŽπš. FAQ

    Public-facing answers for the questions people ask before they trust the framework.

    Open
  2. πš…πš’πš‹πšŽπšŒπš›πšŠπšπšπšŽπš. FAQ β€” ANSWERED

    Answers from the trenches. This is the truth as of April 2026.

    Open