Lay out a four-layer motor driver PCB in KiCad from a finished schematic

A Redditor who designs PCBs had Claude Code on Fable 5.2 lay out a BLDC motor driver board through a KiCad MCP; it routed every trace with its own script and was done in two passes.

Done withClaude Code· Nov 16, 2026

What they did

The poster, who does PCB design for a living and had already built and fabricated this board, gave Claude Code (Fable 5.2 at medium effort) a KiCad 10 project through a KiCad MCP server. The schematic was complete; the layout held only the fixed board outline and mounting holes. The board is a BLDC motor driver with an integrated encoder, an ARGB LED output and a UART header on a four-layer stackup. The prompt set placement rules (encoder centred on the bottom, parts on one side where possible, connectors at the edge), current limits (12 V in, 3 A motor, 1 A LED) and a 20 degree temperature rise for trace sizing, and asked the agent to clarify before starting. As a control, the same prompt, MCP and design rules went to the Codex CLI on GPT Astra 6 at high effort.

How it went

Claude Code asked two questions, including whether the KiCad editor was closed since it would edit the board file on disk. It skipped the autorouter and routed traces with a Python script it wrote, used copper pours on the high current paths, added stitching vias and kept most parts on one side. It took two iterations, the second only moving two traces that sat too close, and used about 96% of a Pro plan session limit. The poster said the result looked like a person had drawn it. The Codex run went past 30 iterations and 1 hour 40 minutes, leaned on the autorouter, put the debug connector in the middle of the board, placed vias in pads and failed the design rule check with unconnected nets.

Worth knowing

This was one run per agent at different effort levels, on a board the poster had already designed, so it is an exercise rather than a production job. A commenter pointed out that Codex asked the sharper electrical questions (phase versus supply current, stall limits). Close the KiCad PCB editor while the agent works, or a save there will overwrite its changes.

Try it

With Claude Code· 8 parts to fill in

Open the KiCad project at [path to project] and do the PCB layout. The schematic is final; the board outline and mounting holes are fixed. It is a [what the board does] on a [number]-layer stackup. Rules: [placement rules, e.g. connectors at the edge, parts on one side]. Size traces for [input voltage], [max currents per rail] and a [allowed temperature rise] rise with [copper weights]. Use copper pours for high current paths and route by hand with a script rather than an autorouter. Ask me anything unclear before you start, then run the design rule check and stop when it passes, showing me any rule you could not meet.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related