VibeBB is Vibe BreadBoarding: describe what you want in plain language, and AI designs the circuit board, enclosure, and firmware — with pass/fail decided by deterministic gates and real-hardware evidence, never by vibes.
The Idea
Vibe Coding let developers fully give in to the vibes and forget the code even exists. VibeBB brings that same conversational loop — see stuff, say stuff, run stuff — to hardware prototyping: boards, enclosures, and firmware.
Just as breadboards made it possible to think by trying — no soldering needed — VibeBB lets you tell the AI what you want to build. Component selection, circuit intent, board layout, enclosure, firmware, and fabrication outputs all follow from the conversation. Not drawing schematics is the hardware counterpart of not reading the code in Vibe Coding.
VibeBB doesn't mean the design or verification is light — it means the heavy verification is hidden from your hands. Where original Vibe Coding skips review entirely, VibeBB moves the reviewer's role from humans to deterministic gates (ERC/DRC, geometry checks, independent re-reads) and measurements on real hardware.
You stay the owner of the requirements. What you check isn't a schematic or copper artwork — it's whether the board that arrives actually works and actually fits in its enclosure. Feedback goes straight back into the next design revision.
The Experience
Long desk studies take a back seat. The default cycle is to build first, verify on real hardware, and immediately spin the next change.
01
Describe what you want to build in natural language. The AI turns the conversation into verifiable requirements.
02
The AI proposes components, layout, enclosure, and firmware. Deterministic checkers — parsers, geometry, ERC/DRC, fab rules — decide pass or fail.
03
Fabrication data goes out; a real board and enclosure come back. You power it up and see if it works and fits.
04
Measurements and real-hardware findings flow back into the design inputs for the next revision. Then the loop runs again.
“Fully give in to the vibes, embrace exponentials, and forget that the code even exists.”
Why Trust It
Three design lanes advance in parallel from the same input files and git history, trading requests with each other — and every outcome is judged by deterministic gates.
Components, circuit intent, placement and routing, ERC/DRC, fabrication outputs. No unverified copper is ever generated.
Outline, component heights, fastening, interference, clearance, wall thickness, CAD output — judged by mechanical measurement gates.
Implementation, build, static checks, and virtual execution delegated to OpenHands' native software capabilities, with pin assignments kept consistent with the board.
Missing tools, parse failures, skipped gates, and unknowns all fail closed. Passing evidence is only produced by digest-pinned container runs.
Every value the AI chose — parts, widths, dimensions, pins — is stored as a typed rationale record alongside the design, so “why this?” is answerable revisions later.
Schematics, PCBs, and drawings are projections generated from input files. Projections never flow back into the source of truth.
Under the Hood
VibeBB is the experience; ACD is the engine. ACD is an AI-first CAD built on OpenHands that inverts the traditional EDA/MCAD model: the AI is the primary designer, and humans own the requirements. The name ACD is an anagram of CAD, symbolizing that role reversal.