Can you vibe code a PCB? What AI can and can't do
Partly. AI tools can help you pick parts, plan a circuit, explain a schematic and write the firmware, and code-based tools like atopile and SKiDL let AI describe a board in text. But layout, power handling and checking the design before you order it still take electrical judgment AI can't supply. Most vibe-coded builds use off-the-shelf modules instead.
The short answer
You can get a long way. AI is genuinely useful for the thinking parts of a circuit board: which parts to use, how they connect, what the datasheet means, and the firmware that runs on it. Where it falls short is the physical part: placing components and routing traces so the board actually works, carries the right current, and can be manufactured.
What AI helps with
- Choosing parts. Ask which regulator, connector or microcontroller fits your project, and why.
- Planning the circuit. It can explain a reference design, suggest decoupling capacitors and pull-up resistors, and list what a minimal board needs.
- Reading datasheets. Paste a section and ask what it means for your design.
- Describing the board as code. Tools like atopile and SKiDL let you define a circuit in text, which AI coding tools can write and edit. KiCad, the free board design tool, can also be scripted.
- Firmware. Once the board exists, AI writes and debugs the code the same way it does for any dev board.
What's still on you
- Layout and routing. Where parts go, trace widths, keeping noisy and sensitive signals apart.
- Power. Current limits, heat, battery charging and protection. Mistakes here can damage parts or start fires.
- Footprints. Checking each part's footprint matches the real part you're buying.
- Design checks. Running KiCad's electrical and design rule checks, and reading the results.
- Anything with mains voltage. Leave it alone unless you're trained.
A safer path to your first board
- Build the project from off-the-shelf modules and get it fully working
- Move it to a breadboard or perfboard with the same parts
- Draw the schematic in KiCad, with AI explaining each part
- Lay out a simple two-layer board, keeping it small and slow
- Run the design rule check and ask someone experienced to look it over
- Order a small batch from a board maker such as JLCPCB or PCBWay, and expect a second revision
Checklist before you order
- Every footprint matches the part you'll actually buy
- Power traces are wide enough for the current
- There's a way to program the board (USB or a header)
- Mounting holes and connectors line up with your enclosure
- The design rule check passes with no errors
When to skip a custom PCB
If a dev board plus modules does the job, use them. A custom board makes sense when you need it smaller, cheaper at volume, or more reliable than a tangle of wires. For a first project, modules win every time.
Related
- What is vibe hardware?
- Best first ESP32 projects
- How AI-buildability is scored, where custom PCB work usually scores 1 or 2
Builds on Afterware with custom boards or open hardware designs are listed below.
