Claude for PCB design

Claude reasons well about circuit trade-offs. It still cannot produce a manufacturable board, and the reason is structural rather than a matter of model quality.

What Claude does well

• +Claude is genuinely useful for picking parts: describe what the circuit must do and it will suggest a regulator, a microcontroller or a sensor family worth considering.
• +It can explain a topology, sanity-check a power budget, or talk you through why a decoupling capacitor belongs close to a supply pin.
• +It can draft a rough netlist in text form, which is a reasonable starting point for a design you intend to verify yourself.

What it cannot do, and why

• −Claude has no geometry engine. It cannot place components on a board with real dimensions, or produce copper that respects clearance.
• −It cannot route a multi-layer board. Routing is a search problem over physical space with hard constraints, not a text-generation problem.
• −It cannot run a design rule check. Without one there is no way to know whether the result is manufacturable.
• −It cannot output fabrication files. Gerber, Excellon drill and pick-and-place data are exact formats that a fab will reject if they are approximated.

The split that actually works

Claude is at its best when you think out loud with it: weighing two regulators, working through a power budget, explaining why a pull-up belongs on a line. Those are judgement calls with more than one good answer. Copper is the opposite: a trace either clears its neighbour by the rule distance or it does not.

That is the line PCBEditor draws. A model handles intent and part choice; placement, routing and the design-rule check are done by code that gives the same board for the same input, so a correct result never depends on how well the model reasoned that day.