AI Flow: JLCPCB

Install?

The JLCPCB ordering stage of AI Flow: from a finished board to assembled boards from JLCPCB. Part substitutes proven from both datasheets, the gerber zip, BOM and CPL from the desktop's own KiCad, every part's rotation checked against JLCPCB's own footprint and corrected, placement-preview evidence, the quote, the human's recorded OK before payment, and rotation corrections shared on component pages. Open source (MIT): build it with ./build.sh.

adom-wiki pkg install adom/adom-aiflow-jlcpcb

Latest: v0.1.8, published

Download for your machine · v0.1.3? ?

AI Flow: JLCPCB

All downloads (1 file)
FilePlatformArchKindSizesha256
adom-aiflow-jlcpcb Linux x64 3.0 MB d0ed92077435478bb06ae419ae192a8b724531c58876abcaa262421a7fcfdb82
Contents

README

markdown

AI Flow: JLCPCB

adom-aiflow-jlcpcb takes a finished board to assembled boards from JLCPCB. It is a stage of AI Flow: the board flow (adom-aiflow) ends at a routed, DRC-clean board, and this app starts there. One Rust binary that tells the AI what to do next and does the deterministic work itself.

Step What happens
intake init from the board release (or the board and BOM), sha256 recorded
sourcing every placed part orderable at JLCPCB; substitutes proven from both datasheets with swap
rules KiCad DRC with JLCPCB's design rules from adom/pcb-design-rules, picked by layer count, on a copy of the board
export gerber zip with paste and drill, JLCPCB BOM and CPL from the desktop's native kicad-cli, then the rotation check
preview JLCPCB's placement preview, a screenshot of every corrected or unverified part
quote, approval, order the total, the human's recorded OK, the order number; nothing is paid without the OK
delivered boards received and tried
share rotation corrections published as jlcpcb-rotation.json on the parts' wiki pages
report what was ordered and the evidence, for the next stage

The rotation check

JLCPCB places each part from the footprint in its own (EasyEDA) library for the LCSC number, at the CPL's rotation. That footprint's zero rotation often differs from KiCad's. For every placed part the check reads JLCPCB's footprint, finds the rotation of 0, 90, 180 or 270 degrees and the offset that land its pads on the board's pads pad for pad, and writes the corrected rotation (and centroid) into the CPL. A part that fits no rotation fails the export. On the 12 V to 5 V buck molecule it found the TPS54202 (TSOT-23-6) at -90 degrees with a 0.012 mm residual, the same correction JLCPCB's preview called for.

Each correction can be shared on the part's component page as jlcpcb-rotation.json (schema adom/jlcpcb-rotation@1), one entry per LCSC number and KiCad footprint, with the evidence counted: pad fits, JLCPCB preview screenshots, boards delivered, distinct users.

Build

Open source, MIT. Rust, Linux.

./build.sh        # tests, release build, bin/adom-aiflow-jlcpcb
./install.sh      # binary to ~/.local/bin, skill to ~/.claude/skills

Desktop steps go through Adom Bridge (adom-bridge) to a Windows desktop with KiCad 10 and pup. Built from the flow-app template in adom/adom-aiflow (template/flow-app).

Evidence checks and access recovery

next checks successful evidence and current board/BOM/artifact hashes, not merely whether JSON files exist, and suggests the step with open items. Nothing is a hard gate (a dynamic skill: suggestions, the AI and the human decide): a later step still runs and notes what is open. Failed rotation parts keep the export open in next; changed exports make the preview evidence stale, and changed previews make the quote stale. Older runs lacking these bindings must regenerate/review their evidence.

Automate JLCPCB in Pup first, reusing one window. Try Sign in with Google inside Pup, select the intended user account, verify sign-in, then continue the saved draft through quote pricing. A sign-in redirect is not a browser failure. Use Native Browser only after a demonstrated Pup-specific failure or explicit user preference.

The separate footprint API can require access recovery while the JLCPCB UI continues in Pup. For that API, use an explicitly selected native browser profile:

adom-aiflow-jlcpcb export --browser-target <desktop> --browser-profile <profile>

Follow the Native Browser skill for owned background sessions and user identity. The native path can use the regional EasyEDA service and reuse today's exact vendor geometry responses. Access denial never becomes a missing-footprint waiver. Quote-only work ends at verified vendor pricing, not payment; the step hints describe recovery and continuation through that boundary.