How WireFrame finds the right part for every BOM row

Where WireFrame looks for a symbol and land pattern, the checks every candidate must pass, why a part you confirm is reused on the next board — and how the AI Copilot reads the same library instead of guessing.

How WireFrame finds the right part for every BOM row

A BOM row is a promise: this part, on this land pattern, with these pins. Get it wrong and the board is wrong however good the schematic looks. This post explains how WireFrame keeps that promise — for parts you add by hand and for parts the AI Copilot plans — and why it is fast enough to run on every row, every time.

The one-line answer: matching is code, not a model. The Copilot may propose a part. Whether it binds is decided by deterministic checks that give the same answer on every run and name the rule when they say no.

Where it looks#

WireFrame first scores everything in the pool against the row:

  • your project's own library (lib_<project>, beside the project file),
  • parts a person confirmed on an earlier project,
  • the libraries you loaded, plus a targeted scan of the library clones on disk — KiCad's official libraries and others.

Only when nothing in the pool passes does it go further: WireFrame's published library (a curated catalogue of 10,000+ parts, each with a symbol, a footprint and usually a 3D model), then LCSC by the row's exact part number, and only then a generated draft that waits for you to confirm it.

The order matters. A real part beats a fabricated one — but a wrong real part is the worst outcome of all, because it looks right. So every candidate, wherever it comes from, passes the same checks.

The Library Manager on the KLP4e datalogger project — the project's own library in the source list, each part previewed with its symbol, footprint and 3D model

For members

Keep reading — it’s free

Sign in or create a WireFrame account to read the rest of this post and every guide on the blog.

  • The rest of this post — about 4 min of reading
  • The same account signs in the WireFrame desktop app
  • Free design tools, no time limit

Sign in to WireFrame

One account for the desktop app and this site.

or with email
Forgot password?

Related posts

What an AI copilot for PCB design should and should not do

Seven rules for an AI that edits your schematic and board: datasheet evidence, a plan before an edit, work on a copy, and a person who approves.

KiCad to WireFrame EDA and back: 72/72 round trips identical

Open a KiCad project in WireFrame EDA, work on it and export it back to KiCad: what comes across, what to check, and how the round trip was measured.

How to design a PCB with Claude over MCP in WireFrame EDA

Connect Claude, Codex or Cursor to WireFrame EDA over MCP and let your own agent design the board you have open: setup, the Allow step, what is counted.