pcb
Skill26k starsChanged 5 days agoMITView on GitHub
Create, edit, lay out and review native KiCad circuit boards (.kicad_pcb) and their schematics (.kicad_sch) - parts and nets, ERC, placement and routing, DRC, and a review before ordering (fab limits, decoupling, track width for current, assembly and BOM sourcing for JLCPCB, PCBWay or another fab); exports fabrication files, the netlist and BOM, or STEP for enclosure design. Shows boards and schematics in the CAD Viewer.
- Pipes a download into a shell
2 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- 1999AZZAR/pcb-skilltheir own version, first seen Oct 20, 2026
- daishuge/pcb-skilltheir own version, first seen Sep 8, 2026
Who's talking about earthtojake/text-to-cad
- GitHub“Open source project of the week: text-to-cad”YouTube · May 31, 2026 · 7.4k views
- Tool Man“Text to CAD: This Free AI Designs Real Parts You Can 3D Print”YouTube · Oct 11, 2026 · 2.3k views
- Alex Hitt“Text-to-CAD GitHub Tutorial: Build123d, STEP Models and AI Agent Setup”YouTube · Sep 8, 2026 · 2.1k views
- The Next New Thing“Text-to-CAD — Describe a Part, Get a Real 3D Model”YouTube · Oct 26, 2026 · 1.8k views
- Blueprint Bytes“Blueprint Bytes | Text-to-CAD: Open-Source AI Harness for Parametric 3D Modeling & CAD Generation”YouTube · Aug 18, 2026 · 1.6k views
The biggest 5 of 88 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 88
Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (88 times).
On GitHub · 50
- Nov 13, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.9 → 0.11.10 — sudosubin/agents.nix0 reactions
- Nov 13, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.9 → 0.11.10 — sudosubin/agents.nix0 reactions
- Nov 13, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.9 → 0.11.10 — sudosubin/agents.nix0 reactions
- Nov 13, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.9 → 0.11.10 — sudosubin/agents.nix0 reactions
- Nov 13, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.9 → 0.11.10 — sudosubin/agents.nix0 reactions
45 more on GitHub
- Nov 13, 2026Docs + example: check parts from CAD agents (text-to-cad, build123d, OpenSCAD) with meshsim — armaan-crypto/meshsim0 reactions
- Nov 13, 2026List meshsim mcp in the official MCP Registry: server.json, README mcp-name marker, release job — armaan-crypto/meshsim0 reactions
- Nov 12, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.8 → 0.11.9 — sudosubin/agents.nix0 reactions
- Nov 12, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.8 → 0.11.9 — sudosubin/agents.nix0 reactions
- Nov 12, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.8 → 0.11.9 — sudosubin/agents.nix0 reactions
- Nov 11, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.8 → 0.11.9 — sudosubin/agents.nix0 reactions
- Nov 11, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.8 → 0.11.9 — sudosubin/agents.nix0 reactions
- Nov 11, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.7 → 0.11.8 — sudosubin/agents.nix0 reactions
- Nov 11, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.7 → 0.11.8 — sudosubin/agents.nix0 reactions
- Nov 11, 2026Update dependencies — maxstreese/maxcad0 reactions
- Nov 11, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.7 → 0.11.8 — sudosubin/agents.nix0 reactions
- Nov 11, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.7 → 0.11.8 — sudosubin/agents.nix0 reactions
- Nov 11, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.7 → 0.11.8 — sudosubin/agents.nix0 reactions
- Nov 11, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.6 → 0.11.7 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.4 → 0.11.7 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.6 → 0.11.7 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.6 → 0.11.7 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.6 → 0.11.7 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.5 → 0.11.6 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.5 → 0.11.6 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.5 → 0.11.6 — sudosubin/agents.nix0 reactions
- Nov 10, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.4 → 0.11.6 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.4 → 0.11.5 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.4 → 0.11.5 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.4 → 0.11.5 — sudosubin/agents.nix0 reactions
- Nov 9, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.3 → 0.11.4 — sudosubin/agents.nix0 reactions
- Nov 9, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.3 → 0.11.4 — sudosubin/agents.nix0 reactions
- Nov 9, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.3 → 0.11.4 — sudosubin/agents.nix0 reactions
- Nov 9, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.3 → 0.11.4 — sudosubin/agents.nix0 reactions
- Nov 9, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.3 → 0.11.4 — sudosubin/agents.nix0 reactions
- Nov 9, 2026Reference health: open findings — Valpatel/cad-agent0 reactions
- Nov 9, 2026vendor: pull text-to-cad 1cfd73cb — gurul/gencad0 reactions
- Nov 8, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.1 → 0.11.3 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.1 → 0.11.3 — sudosubin/agents.nix0 reactions
- Nov 8, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.2 → 0.11.3 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.2 → 0.11.3 — sudosubin/agents.nix0 reactions
- Nov 8, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.1 → 0.11.3 — sudosubin/agents.nix0 reactions
- Nov 8, 2026Update dependencies — maxstreese/maxcad0 reactions
- Nov 8, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.1 → 0.11.2 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.1 → 0.11.2 — sudosubin/agents.nix0 reactions
- Nov 8, 2026agent-skills.github.earthtojake.text-to-cad: 0.11.0 → 0.11.1 — sudosubin/agents.nix0 reactions
- Nov 8, 2026codex-plugins.github.earthtojake.text-to-cad: 0.11.0 → 0.11.1 — sudosubin/agents.nix0 reactions
- Nov 8, 2026agent-plugins.github.earthtojake.text-to-cad: 0.11.0 → 0.11.1 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-plugins.github.earthtojake.text-to-cad: 0.11.0 → 0.11.1 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-marketplaces.github.earthtojake.text-to-cad: 0.11.0 → 0.11.1 — sudosubin/agents.nix0 reactions
On YouTube · 22
- May 31, 2026Open source project of the week: text-to-cad — GitHub7.4k views · 3 comments
- Oct 11, 2026Text to CAD: This Free AI Designs Real Parts You Can 3D Print — Tool Man2.3k views · 1 comment
- Sep 8, 2026Text-to-CAD GitHub Tutorial: Build123d, STEP Models and AI Agent Setup — Alex Hitt2.1k views
- Oct 26, 2026Text-to-CAD — Describe a Part, Get a Real 3D Model — The Next New Thing1.8k views
- Aug 18, 2026Blueprint Bytes | Text-to-CAD: Open-Source AI Harness for Parametric 3D Modeling & CAD Generation — Blueprint Bytes1.6k views
17 more on YouTube
- Oct 5, 2026text-to-cad — Dann Paker AI1.2k views
- Oct 7, 2026Text-to-CAD: Give Your Agent CAD Superpowers — CLI Stack818 views · 1 comment
- Jul 24, 2026earthtojake/text-to-cad — Prompt in, real CAD out. 🟡 Watchlist #Shorts — ForkCast781 views
- Sep 10, 2026earthtojake/text-to-cad: AI Agent Skills for CAD, CAM, and CAE Design — SkipCI606 views
- Oct 6, 2026text-to-cad: Design Parts with Your AI Agent | GitHub Repos You Should Know #005 — GitHub Repos You Should Know492 views
- Oct 7, 2026text-to-cad: Give Your AI Agent Real CAD Superpowers — Open Source Trend310 views
- Oct 10, 2026Claude Code + text-to-cad: How to set up free in 4 minutes — OverClocked254 views · 1 comment
- Oct 30, 2026text-to-cad: give your AI agent CAD skills — RepoRadar249 views
- Oct 30, 202624.3K ⭐ Your AI Agent Can Design 3D Parts You Can Print — Github God Eng150 views
- Jul 23, 2026earthtojake/text-to-cad - Gource visualisation — Gourcer138 views
- Oct 19, 2026Text-to-cad: give your agent CAD superpowers — Next Horizon111 views · 1 comment
- Oct 7, 2026Text To Cad | GitHub Daily | 2026-10-06 — Insight AI102 views
- Oct 28, 2026🚀 [Fastest Growing GitHub Repos] text-to-cad: The Free Tool Taking Over GitHub! #shorts — githubrepo_cloud83 views
- Oct 8, 2026Text-to-CAD: Your Agent Designs Real Parts — Business Builder82 views
- Oct 13, 2026Codex Can Now Design Parts You Can 3D Print (Free text-to-cad) — Blake AI Search80 views
- Sep 16, 2026Text-to-CAD Tested by an AI Agent: 1 mm Walls Passed the Build, Validator and Slicer — README to Realitysays it tested it32 views
- Oct 24, 2026This FREE AI Tool Turns a Sentence Into a Real 3D-Printable Object (text-to-cad) — RepoExplained27 views
On Bluesky · 10
- May 18, 2026Text-to-CAD open source : décrivez une pièce ou un mécanisme en langage naturel, laissez un agent (Codex, Claude Code) générer les fichiers… — @camilleroux.com14 likes and reposts · 1 reply
- Nov 3, 2026Give your AI agent CAD superpowers: real STEP and STL files, manufacturing checks and engineering drawings. 🔗… — @prosperflowio.bsky.social2 likes and reposts
- Jul 28, 2026github.com/earthtojake/... — @davepentecost.bsky.social2 likes and reposts · 2 replies
- Jul 31, 2026text-to-cad is a library of eleven agent skills that turn a coding agent into a CAD engineer, carrying a plain-language request from STEP… — @agentpalisade.bsky.social1 likes and repost
- Jul 30, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 earthtojake / text-to-cad ⭐ 11,679 (+477) 🗒 JavaScript A collection of agent skills for CAD,… — @github-trending-js.bsky.social1 likes and repost · 1 reply
5 more on Bluesky
- Jul 25, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 earthtojake / text-to-cad ⭐ 10,288 (+555) 🗒 JavaScript A collection of agent skills for CAD,… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Jul 22, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 earthtojake / text-to-cad ⭐ 8,784 (+297) 🗒 JavaScript A collection of agent skills for CAD,… — @github-trending.bsky.social1 likes and repost · 1 reply
- Jul 21, 2026今日のGitHubトレンド earthtojake/text-to-cad CAD、ロボティクス、およびハードウェア設計を行うAIエージェント向けのスキルライブラリです。 CADデータの生成、検査、調達、スライス、受け渡しなどの機能をエージェントに提供することを目的としています。 — @dailygithubtrends.bsky.social1 likes and repost
- Aug 8, 2026公式GitHubを確認。これはかなり堅い。CADを会話だけで終わらせず、ソース管理されたファイルとして編集し、STEP/STL/URDF/SRDF/SDFやG-codeまで明示的に出力・閲覧する技能群。… — @nemu-echosphere.bsky.social0 likes and reposts · 1 reply
- May 25, 2026CAD SKILLS: Generate CAD in AI agents like Codex and Claude Code. 100% open source, runs locally, free forever. 开源生成 CAD 文件的代理模型 - 支持导出… — @maoguofang.bsky.socialsays it tested it0 likes and reposts · 2 replies
On the web · 4
- Nov 3, 2026earthtojake/text-to-cad · 25.0K Stars · GitHub 趋势| open-repo — open-repo.com
- Oct 15, 2026Struggling with CAD tools? Check out text-to-cad, an open ... — instagram.com
- Aug 15, 2026An incredible new open-source venture called text-to-cad has ... — instagram.com
- May 20, 2026new release for text-to-cad, an open source CAD harness ... — x.com
On Hacker News · 2
- May 1, 2026Text-to-CAD186 points · 48 comments
- Apr 29, 2026Text-to-CAD: Generate 3D models with coding agents (open source)2 points
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- daishuge/pcb-skill★ 136same name
- 1999AZZAR/pcb-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cadSkill
- engineering-drawingSkill
- feaSkill
- print3dSkill
- renderSkill
- robot-simulationSkill
- sendcutsendSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run the cad command (~/.local/bin/cad where it is not on your PATH.
- Very specific: line 119
Use the typed commands first (cad kicad_pcb drc|export, cad kicad_sch erc|export): their results are the ones the checks and the viewer …
- Distinctive: line 147
Check the saved board after every step, from the same revision you will hand over:
- Distinctive: line 183
Use the selected fab's own capability page for the board's layer count, copper weight and finish.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PCB design
Setup
Run the cad command (~/.local/bin/cad where it is not on your PATH; cad.exe on Windows). If
it is missing, install text-to-cad, outside a sandbox or with its permission:
curl -fsSL https://texttocad.dev/install.sh | shOn Windows, in PowerShell: irm https://www.texttocad.dev/install.ps1 | iex. If the CAD app was
only just added, its server may still be starting: try again for up to a minute first. cad doctor
--check explains any other failure, changing nothing; cad doctor repairs what it reports. Tell the
person any next step cad setup prints.
text-to-cad reads a board or schematic itself, so inspecting either, and viewing a schematic or taking
its snapshot, need no KiCad. DRC (cad kicad_pcb drc), ERC (cad
kicad_sch erc), every export (cad kicad_pcb export, cad kicad_sch export) and an edit
(kicad_pcb.edit, kicad_sch.edit) run KiCad's command line, kicad-cli,
and its IPC API from kicode, the kicad extra (cad[kicad]): the cad command installs it the first
time a board command needs it (about 100 MB to download and 340 MB on disk, once; nothing for you to install), and cad run gives a
script that edits a board its environment. Showing a board or taking its snapshot needs it too: KiCad
refills the board's copper pours on a copy before they are drawn, so the first board shown starts that
download. CAD_KICAD_REFILL=0 in the server's environment turns the refill off (no download; set
it as CAD_KICAD_3DMODELS below), and the pours are drawn as the file saved them, as they are when the
download or the refill fails. A KiCad you installed yourself is never run. CAD_KICAD_CLI can name
another kicad-cli (the command line itself, named kicad-cli; KiCad 9 or newer, a nightly's for an
edit). It runs headless, with private settings, and never opens KiCad's app; never open a
board in KiCad's app to check it. Its library variables name KiCad's own libraries, never your
variables or KiCad settings: a project's sym-lib-table or fp-lib-table row that names a stock
library as KiCad's own tables do (${KICAD10_SYMBOL_DIR}/Device.kicad_sym,
${KICAD10_FOOTPRINT_DIR}/Resistor_SMD.pretty, any major's spelling) reads it in the libraries of the
KiCad you installed (the newest, if several; or the installation whose 3dmodels folder
CAD_KICAD_3DMODELS names): nothing to set. With no KiCad installed, ERC warns lib_symbol_issues that
each such library was not found and DRC lib_footprint_issues that it is not enabled; a project that
carries its libraries (${KIPRJMOD}) needs no KiCad.
kicode's KiCad is a nightly (10.99), so a board or schematic it saves is in the nightly's format, which a stable KiCad app refuses; viewing and snapshots still work, and the CAD Viewer's Open in says which KiCad on this computer can open the file.
Native files are the source
Edit the .kicad_pcb itself, preserving its companion .kicad_pro, .kicad_dru, libraries and
schematic when present. Reading or displaying a board never writes it. There is no text-to-cad PCB
model, build step, or generated-board ownership marker. A helper script may make a requested edit,
but reread the current file before editing and preserve unknown records and UUIDs. Do not regenerate
an existing project from an incomplete description.
Change a board through KiCad's IPC API in an edit, a with block: kicad_pcb.edit hands the block the
open board (KiPy's Board, as kicode names it: kicode.board.Board) and saves it at the block's end
when the block changed it; a block that changes nothing leaves the file byte for byte, one that raises
saves nothing (its exception goes on), and a save KiCad cannot finish leaves every file as it was,
saying why. A board not there yet is made by KiCad, with its project,
and saved. kicad_sch.edit does the same for a schematic (schematic);
the two of one project, one inside the other, share one KiCad. Run the script with cad run board.py,
which gives it the kicad extra (kicode: KiPy and a kicad-cli with its headless api-server); a
kicad-cli that CAD_KICAD_CLI names without one is refused up front, before any server starts. That
server listens on a local socket, which a shell sandbox that refuses sockets (an agent app's default, Codex's
among them) does not allow: the edit then stops at once, saying so, and the script must run outside the
sandbox (ask for the unsandboxed or escalated run); inspecting, DRC, exports and snapshots run inside it.
KiCad's first start from a new environment can take a minute, which the edit says while it waits. Import
KiPy's names from kicode (from kicode.proto.common.types import KIID, from kicode.util.units import
from_mm), never from kipy: the two cannot share a process. Saving writes the file in the nightly's
format: one from an older KiCad is upgraded, which the run says, and that older KiCad can no longer open
it. Checks and exports of the saved board are calls after the block (kicad_pcb.drc, kicad_pcb.export);
a STEP or GLB export holds each part's 3D model where the board's 3D view finds it (board
views), and leaves out, naming them, the parts whose model is missing (or, in a STEP, only in
VRML); --to dxf writes the outline and drilled holes, for an enclosure:
from cad import kicad_pcb
from kicode.util.units import from_mm
BOARD = "board.kicad_pcb"
with kicad_pcb.edit(BOARD) as b: # the board file is the source; the block edits it in place
power = [t for t in b.get_tracks() if t.net.name in {"+5V", "+3V3"}]
for track in power:
track.width = from_mm(0.8)
b.update_items(power)
b.refill_zones()
drc = kicad_pcb.drc(BOARD)
if not drc.ok:
raise SystemExit("\n".join(drc.human_lines())) # each finding, then FAILED and the count
for kind in ("gerbers", "drill", "pos", "bom", "step"):
kicad_pcb.export(BOARD, to=kind, out=f"fab/{kind}")An edit states the result it wants, so running it again is harmless: "U1 is at (10, 20)", "the power tracks are 0.8 mm", never "move U1 5 mm" or "widen the tracks by 0.2 mm". Set absolute positions, rotations, widths and nets; create an item only when the board does not hold it yet (find it first by its reference, net or place). A script stopped halfway and run again then ends where one run would.
A board's design starts at its schematic, which says what connects to what: read it, check it with
ERC and look at each sheet (schematic) before laying out, and hold the board
to it after. For creation or structured edits read native files. For parts and
footprints read parts. To place and route a board, read
layout: start from the schematic's netlist, place one part or functional
group at a time (placement says in what order and where), route the nets
whose path matters by hand and direct the router (cad.kicad.route in the edit, with the plan you
give it; never a third-party autorouter) through the rest, octolinear, with widths for each net's
current, and check each step with cad kicad_pcb drc, the copper stills and a script of the layout's own properties. KiCad's file coordinates are millimetres, y down;
footprint-local positions and rotations must be transformed into the board frame. Use a net's
actual pad positions when routing. Check the datasheet's pin numbers, footprint orientation and
connector mating side; a plausible-looking layout does not establish electrical correctness.
KiCad's own command line
Use the typed commands first (cad kicad_pcb drc|export, cad kicad_sch erc|export): their results are
the ones the checks and the viewer read. For anything they do not cover, run KiCad's own command line
with cad run kicad-cli …: the pinned kicode kicad-cli with its own subcommands and flags (cad run
kicad-cli pcb --help), no --with needed, headless with private settings, its output and exit code
KiCad's. CAD_KICAD_CLI does not change which one runs.
cad run kicad-cli pcb render --side top --rotate -45,0,45 -o tmp/board.png board.kicad_pcb
cad run kicad-cli project downgrade --dry-run --target 10.0 board.kicad_pro # then -o DIR without --dry-runMost commands write only their -o, though kicad-cli may leave a .kicad_prl beside a board it reads.
These rewrite the source: pcb upgrade and sch upgrade, fp upgrade and sym upgrade without -o,
and pcb drc --refill-zones --save-board. project downgrade exits 2 without writing when the target
cannot represent the board.
Edit
- Inspect the saved board with
from cad import kicad_pcbin a script run withcad run; record the parts, nets, outline, relevant dimensions and constraints before changing it. Checks documents this read-only API and clickable references. - Edit the board in a
kicad_pcb.editblock (or, as a fallback, the native file). Keep net assignments, layer stack, track widths, clearances and custom rules consistent with the chosen fab and electrical requirements. Refill changed copper zones with KiCad (b.refill_zones()in the block) before relying on their saved fill.
Check each change
Check the saved board after every step, from the same revision you will hand over:
| The change | Check it with |
| The schematic | cad kicad_sch erc board.kicad_sch (KiCad's ERC: errors fail it) and cad kicad_sch snapshot board.kicad_sch tmp/sheet.png --sheet /Power/ for each sheet changed (schematic) |
| Board against schematic | the pin-by-pin comparison in schematic: every pad on its schematic pin's net |
| Anything: parts, copper, zones, rules | cad kicad_pcb drc board.kicad_pcb (or --json): KiCad's DRC against the board's own rules (its .kicad_pro's; without one, KiCad's defaults, which it warns about as no_project). It exits 1 on error-severity violations or unconnected items. Unconnected items are the routing still to do |
| Placement | cad kicad_pcb snapshot board.kicad_pcb tmp/placement.png --display placement: short, uncrossed ratsnest lines mean a group is placed well; measure decoupling distance and connector access with kicad_pcb.read |
| Routing | The layout's property script (layout): segments off 45 degrees, detours, width for current |
| How copper and silkscreen look | cad kicad_pcb snapshot board.kicad_pcb tmp/copper.png --display copper (and --display '{"mode":"copper","side":"bottom"}') |
| Ready to order | The review below |
- Review warnings too: KiCad's silkscreen, mask and courtyard rules are warnings, and they are what a fab's CAM engineer flags.
- Resolve the cause instead of weakening rules to obtain a clean report.
- A clean DRC establishes the board's own rules, nothing more: not the circuit's correctness and not the fab's limits. A number is never read off a snapshot.
Before ordering
A review of one board, for the fab and assembler it will be ordered from, is a guided review, not a
fab's own engineering check: report what was not checked. Gather evidence in this order: KiCad's DRC
(every error blocks ordering); then measurements DRC cannot make, from the board read back with
kicad_pcb.read and the project BOM; then the checklist of what no command measures, with a snapshot.
| Area | Reference | Measured by |
| Fabrication | review-fabrication | KiCad's DRC against the board's rules; the rest by inspection |
| Electrical | review-electrical | the board read back: decoupling distances, narrowest track per net |
| Assembly and sourcing | review-assembly | the part list and placement file, by inspection |
Each finding names its parts by board reference (U2, C8, #net:VBUS); kicad_pcb.read(path).resolve(ref)
says where one is.
Choosing the rules
- Use the selected fab's own capability page for the board's layer count, copper weight and finish. The project's Board Setup and custom rules may differ from the fab's limits: compare them.
- Where the person names no fab, review against JLCPCB's standard service and say so.
- Record the source, its date and the conditions (layers, copper, finish) with every limit you adopt. If it cannot be checked, report the missing rule rather than invent one.
A fab's standard tier is a price, not a physical limit: finer work is often possible at a surcharge. Say which it is.
The review
Scope first: board file and revision, fab and service, layers, copper, finish, assembled or bare. Then the findings, errors first, each with where (board references), the evidence (the command or measurement), the rule and its source, the result and the fix; then the coverage: checks run, and checks not run with what they need. No findings is not a manufacturability approval.
| Item | Evidence | Rule | Result | Fix |
U2 pad 3 to C8 | measured 3.67 mm centre to centre from the board read back | decoupling within 3 mm (this review's guide) | review | move C8 beside pin 3 |
pass for a measured item within a cited limit; fail for a measured violation or a KiCad error; review for a risk a person decides; unverified where evidence or the fab's rule is missing. Keep cost suggestions (basic vs extended parts, a cheaper finish) apart from manufacturing constraints. A review alone does not ask for edits or an order: fix only when asked, then check the neighbours of every fix (a moved capacitor can open a clearance elsewhere). Never order on the person's behalf.
Export only the requested deliverables from the saved revision you checked; see manufacturing and STEP. A DRC or ERC error blocks writing fabrication files (Gerbers, drill, placement, BOM, ODB++, IPC-2581) unless the person explicitly says to go ahead; the report then names every error they went ahead with.
Show the model
Show the person each model you create or change, and any model or file they ask to see. If your
tools include cad_show (your host may prefix it), call it with the model's id or the file's
absolute path; its description says the rest. Otherwise give the person the page's link once, to
open in the app's browser pane where it has one, or their browser: a model's page is the view: line its run prints, and a file's is the url that
cad viewer --json FILE [FILE ...] prints for it (never guess the port). A file you export is a
download: give its path. Never screenshot the viewer to check your own work; review with
cad <type> snapshot. If it fails to launch, say so.
Board views
The board view supports layers, selection, Measure, annotations and Quick Edit, in 2D and in 3D.
Select works as KiCad's: a click picks a part, pad, track, via, zone, rule area, text, dimension or
graphic, as its Selection Filter ticks them (locked items only when the person ticks them), and a
drag draws a box that takes anything it touches. A box that takes nothing names an area, a box on the layer the person works on
(#F.Cu@x10y5..x20y15). The panel at the left (⌘\ or Ctrl+
hides and shows it, / searches it) has one search over three tabs. Parts lists the parts in the
schematic blocks their footprints record (by kind on a board that records none): a block picks every
part in it. Nets lists the nets: a net picks the whole net. Each arrives as a reference
(checks says what each names and how to resolve it). Layers
lists the layers: each layer's eye, and a press for the active layer (drawn on top); under them, how
the board is drawn: Other layers (KiCad's high-contrast modes: the layers but the active one
Shown, Dimmed or Hidden, Ctrl+H cycling them; the outline, and the drills and vias
through an active copper layer, always stay at full strength), the copper pours and the zones' and
tracks' opacity; last, 3D models, how many parts stand on a model in 3D, with its eye. Under the
tabs, the picked part's or net's pads. The tool strip ends, after its rule, with Flip (the side
seen: the board as two stacked layers, the side facing you solid; ⇧F), 2D/3D (reading 2D while the
board is flat, 3D in 3D) and Display (the preset: the mode); the zoom is the pill at the
bottom-right. Flip's and 2D/3D's icons are what is on screen and their tooltips what a press does. These are the display, so a Quick Edit's packet
draws the same. The board follows the app's theme: KiCad's colours on the dark canvas, and on the
light one the same colours darkened enough to read (copper stays KiCad's red and blue).
In 3D (2D/3D, or the key 3) the board is a slab whose two faces are drawn as the 2D view draws
them, each part standing its 3D model. A press picks what the 2D view picks where the pointer's ray
meets the face, or the part whose body is in front of it; a drag turns the view; Flip (or ⇧F)
turns the camera over, and its icon shows the side the camera is on. A part's model is the STEP its footprint names, looked for only in the
board's folder (${KIPRJMOD}), KiCad's installed 3D library (every ${KICADn_3DMODEL_DIR}) and the
folders CAD_KICAD_3DMODELS names (separated as PATH is); a .wrl name is read as the .step or
.stp beside it. CAD_KICAD_3DMODELS is read from the server's environment: a server already
running does not see a variable set in a shell afterwards, so set it before the server starts
(cad stop, then run any cad command with it set). A part without a model stands as a block, and
Parts lists it under No 3D model, with why: VRML only (no STEP beside the VRML), not found,
outside the folders above, too large, not a STEP, embedded in the board, or too many models.
cad kicad_pcb inspect board.kicad_pcb --json reports each model the same way (models: found,
missing with the reason, and the parts that name none), and a STEP or GLB export (cad kicad_pcb export
--to step|glb, kicad_pcb.export) holds exactly the models found, a CAD_KICAD_3DMODELS read from
the command's environment. cad run kicad-cli reads KiCad's library as KiCad does: every
${KICADn_3DMODEL_DIR} is the first of those library folders, and a .wrl name needs its .wrl file
there (KiCad 10's library ships STEP alone), so prefer the typed export.
Snapshots use cad kicad_pcb snapshot, including --job packets saved by Quick Edit. Display modes
are board, copper, assembly, and placement. A still is always light (the light canvas and its
colours), whatever the viewer's theme, as every snapshot is:
cad kicad_pcb snapshot board.kicad_pcb tmp/copper.png --display copper
cad kicad_pcb snapshot board.kicad_pcb tmp/bottom.png --display '{"mode":"copper","side":"bottom","poured":false}'
cad kicad_pcb snapshot board.kicad_pcb tmp/front.png --display '{"layers":["F.Cu","Edge.Cuts"]}'
cad kicad_pcb snapshot board.kicad_pcb tmp/inner.png --display '{"active":"In1.Cu","others":"dimmed","zones":0.3}'
cad kicad_pcb snapshot board.kicad_pcb tmp/front-only.png --display '{"active":"F.Cu","others":"hidden"}'
cad kicad_pcb snapshot board.kicad_pcb tmp/u1.png --window 108,42,132,66 --width 1600--window X0,Y0,X1,Y1 draws only that box of the board, filling the picture: two opposite corners in
KiCad's millimetres (y down, the box board.area(x0, y0, x1, y1) names), as close as a fan-out or a
finding needs (--window=-10,5,20,30 when the first is negative). With --width alone the height
follows the box's shape. It goes with any display (--display copper), and takes no --camera.
Bottom views mirror the board and its annotations. Native 2D snapshots support the board's plan
camera, layer visibility and saved ink; they do not support 3D Preview, pose or transparency.
The viewer and snapshots draw the board as KiCad's PCB editor shows it (front copper active, pours
at 60%, pad numbers and net names on pads, vias and tracks, dimensions; no drawing sheet, the board alone); they approximate mask/paste openings
and use stroke lettering, KiCad's text markup (~{RESET}, IO_{3}, x^{2}) drawn as KiCad draws it on
silkscreen, fab and copper text, fields and net names; text boxes, tables and embedded images are not drawn. KiCad's DRC and manufacturing
exports remain authoritative for fabrication. For an enclosure use KiCad's STEP export, not a
solid inferred from the 2D plot.
Schematic views
cad viewer --json board.kicad_sch opens a schematic a sheet at a time, with the board view's
selection, Measure, annotations and Quick Edit, and its panel: one search over Parts, Nets
and, for more than one sheet, the Hierarchy. The Hierarchy is KiCad's
Hierarchy Navigator: a press shows that sheet. A double-click on a sheet symbol enters it, and the
Hierarchy goes back up; a sheet shown again is where it was left. Select works as KiCad's: a click picks a symbol, pin, wire, label, sheet,
junction or no-connect, as its Selection Filter ticks them, and a drag draws a box that picks anything
it touches.
Parts lists the parts by the sheet they are placed on, each with its pins, and Nets the nets
with the pins on them. A net picked there lights across the sheet shown, and a part on another sheet shows
that sheet. Each arrives as a schematic reference (#R1, #R1.2, #net:/MID, #sheet:/Power/,
#wire:<uuid>; schematic says what each names). The schematic follows the
app's theme: KiCad's paper and ink in light, a dark sheet with light ink of the same hues in dark. Each
sheet is on KiCad's default drawing sheet, as its schematic editor shows it: the frame with its zone
numbers and letters, and the title block filled from that sheet's own title block (a project's own
.kicad_wks is not drawn; the default stands in). ERC findings are not drawn: run cad kicad_sch erc. The file
menu's Export offers KiCad's PDF, SVGs, netlist and BOM. Snapshots use cad kicad_sch snapshot, and
a Quick Edit packet carries the sheet the view showed, on the whole drawing sheet as the viewer showed it (border). A still is always on KiCad's light paper,
whatever the viewer's theme, with KiCad's default title block ("title": false leaves it out; border
adds the page's edge and frame) and text markup (~{RESET}, IO_{3}) drawn as KiCad draws it:
cad kicad_sch snapshot board.kicad_sch tmp/power.png --display '{"sheet":"/Power/","border":true}'
cad kicad_sch snapshot board.kicad_sch tmp/power-plain.png --sheet /Power/ --display '{"title":false}'Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

