pcb
Skill1 starsChanged 2 months agoMITView on GitHub
Design a manufacturable PCB end to end — concept, schematic, layout, routing, verification, and a staged purchase — driven from Claude Code, Codex, or Antigravity on the desktop, with KiCad (kicad-cli, pcbnew, and direct S-expression design) and JLC/LCSC/Taobao in a logged-in browser. Optimises for cost-effectiveness, hand-assembly, and a free prototype board.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- earthtojake/text-to-cadtheir own version, first seen Nov 8, 2026
- daishuge/pcb-skilledited, first seen Sep 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- daishuge/pcb-skill★ 13690% same
Wrote their own version · 1
- earthtojake/text-to-cad★ 26ksame 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.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
性价比 — cost-effectiveness: Every part is chosen on measured price and real availability, netted against stock the user already owns.
- Distinctive: line 27
Do not begin design work until these are true.
- Very specific: line 33
An approval watcher: if the platform pops permission cards for every browser action, or the agent blocks on a card it cannot press itself.
- Very specific: line 41
Read references/01-workflow.md for the full version.
- Distinctive: line 56
A green board is not a correct board: Every phase ends with a one-pass, read-only, adversarial review by a fresh reviewer that re-derives …
- Very specific: line 76
Thermal starvation on passives (
starved_thermal): If project rules enforce $\ge 2$ spokes, SMT passives on flood margins may starve. - Very specific: line 91
Every PCB design project MUST conclude with a cleanup pass to ensure a uniform deliverable directory across all projects (e.g.
- Very specific: line 92
Remove all intermediate generator scripts (gen_*.py, assert_netlist.py), test boards (test_*), raw netlists (*.net), and debug dumps …
≈ “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
Take a hardware idea to a board a human can actually order, solder and bring up.
This skill is written from a real project that went from a blank page to a released 4-layer board. Most of what is here is not PCB theory — it is the specific set of failures that theory does not catch, and the gates that catch them.
The three principles this skill optimises for
- 性价比 — cost-effectiveness. Every part is chosen on measured price and real availability, netted against stock the user already owns. A price nobody has read off a live page is an ESTIMATE and must be labelled as one.
- 好装配 — assemblable by hand. The user solders this. No QFN/DFN/exposed-pad-only packages unless the user says otherwise. Every pad reachable with an iron, in an order that does not trap a joint behind a tall part.
- 免费 PCB — the board should cost nothing. JLC's free-prototype coupon has hard geometric and process limits. Design inside them from the first sketch, not at the end.
Before you start — the environment must be ready
Do not begin design work until these are true. Check, do not assume.
- KiCad (v9 native, v7+ compatible) installed, with
kicad-cliandpcbnewanswering (kicad-cli --version). Native KiCad 9 formats:(version 20250114)for.kicad_schand(version 20241229)for.kicad_pcb. Seesetup/kicad-setup.md. - A browser with the agent extension, logged in to the sites the project needs:
Taobao, JD, JLC/LCSC. See
setup/browser-logins.md. - An approval watcher if the platform pops permission cards for every browser action,
or the agent blocks on a card it cannot press itself. See
setup/auto-approve-*.md. Carts and payment stay manual — the watcher is deliberately bypassed there. - A notification channel for long runs (
scripts/notify/), so silence is never ambiguous.
The workflow — four phases, each with a gate
Read references/01-workflow.md for the full version. In outline:
| phase | produces | gate before moving on |
| 1 Concept | what it does, for whom, the hard vs soft constraints | the user has answered every question whose two answers give different boards |
| 2 Schematic + sourcing | full schematic, priced BOM, staged carts | netlist assertions pass; ERC clean (kicad-cli sch erc); every price VERIFIED or labelled ESTIMATE |
| 3 Layout + routing | placed, routed, poured board | placement is routable, not merely legal; DRC 0/0 (kicad-cli pcb drc); adversarial review clear |
| 4 Fabrication + purchase | verified Gerber, order at the pre-payment page | the package is verified independently of the EDA that produced it (export_jlcpcb.py) |
Never place an order or pay. Drive to the pre-payment page and stop.
The rules that actually caught the bugs
These are load-bearing. references/02-review.md explains each with the failure it caught.
- A green board is not a correct board. Every phase ends with a one-pass, read-only, adversarial review by a fresh reviewer that re-derives the numbers instead of reading them. Write its termination criterion before it starts, or it will loop.
- Measured, not inferred. "X probably does not support Y" is not a finding. If a claim decides whether work continues, prove it. Say which numbers were measured and which were computed.
- A wait condition must answer: if this crashed right now, would my filter emit a line? Watchdogs cover four terminal states — output present, crash signature, process gone, wall-clock timeout — plus a progress-rate floor.
- Verify the tool before trusting the result. Three separate checkers on this project silently measured the wrong thing (a cached 3D model, a bounding box instead of a pad, a merged copper label). Calibrate every geometric transform against a known asymmetric object.
- Rule area / keepout trap (
pcbnew.ZONE):SetIsRuleArea(True)in KiCad 9 defaults to blocking tracks, vias, AND pads while allowing copper pour. For copper-pour-only keepouts (antennas, crystals, USB-C), you MUST explicitly setSetDoNotAllowCopperPour(True)and disable track/via/pad blocking (SetDoNotAllowTracks(False), etc.). - Unconnected Zone [GND] at (1.0, 1.0) is an island diagnosis: DRC pointing to (1.0, 1.0)
is reporting the zone origin, not the defect. Dense routing creates isolated copper islands
on F.Cu or B.Cu. Use
zone.GetFilledPolysList()to locate sub-polygons lacking PTH/via connections and bridge them with stitching vias. - Thermal starvation on passives (
starved_thermal): If project rules enforce $\ge 2$ spokes, SMT passives on flood margins may starve. Usepad.SetLocalZoneConnection(pcbnew.ZONE_CONNECTION_FULL)for solid connection. - Rotated pad geometry is anisotropic: Pads at 90° swap width and height in global board space. Evaluate rotated coordinates plus solder mask expansion ($0.05,\text{mm}$) when checking trace clearance.
- Connector Mating Orientation Traps (
connector_rules.py): KiCad footprints do NOT share a uniform 0-degree mating angle: USB-C points South (+Y) at 0°, while Audio Jacks point West (-X) at 0°. Rotating by intuition causes connectors to face backwards into the board. Always compute exact edge orientations withscripts/kicad/core/connector_rules.py(USB-C West=270°, East=90°; Audio Jack East=180°, West=0°). - Pre-flight Placement & Clearance Engine (
placement_validator.py): Never guess placement coordinates or iterate blindly through DRC errors. Runkicad_ctl.py audit-placementbefore routing to mathematically audit true courtyard overlaps (F.CrtYd), connector edge alignments, and $\ge 0.5,\text{mm}$ board-edge clearances in $<100,\text{ms}$. - Standardized Deliverable File Structure & Clean-up (Zero Bloat):
Every PCB design project MUST conclude with a cleanup pass to ensure a uniform deliverable directory across all projects (e.g.
keyboard_555,esp32c3_controller,stereo_mixer_4ch).- Remove all intermediate generator scripts (
gen_*.py,assert_netlist.py), test boards (test_*), raw netlists (*.net), and debug dumps (*.json,*.log,*missing3Dmodels.txt). - Synthesize all mission constraints, circuit calculations, architecture decisions, BOM, and verification stats into a single comprehensive
README.mdwith 3D render previews (jlcpcb_production/*_render_top.pngand*_render_bottom.png). - Export standard
<project>-drc.rptand<project>-erc.rpt. - The root directory must strictly contain ONLY:
jlcpcb_production/(Gerber zip, BOM, CPL, 3D renders)<project>-drc.rpt<project>-erc.rpt<project>.kicad_pcb<project>.kicad_sch<project>.kicad_pro<project>.kicad_prlREADME.mdfp-info-cache
- Remove all intermediate generator scripts (
- The last honest step is the user's. Logins, CAPTCHAs, and payment are theirs. Prepare everything else so their part is two minutes.
References — load what the current phase needs
| file | when |
references/01-workflow.md | always, at the start |
references/02-review.md | before every review, and when writing any checker |
references/03-jlc-manufacturing.md | before fixing the board outline, stack-up or rules |
references/04-sourcing.md | choosing parts, pricing, netting against stock, staging carts |
references/05-kicad-workflow.md | driving KiCad headlessly via CLI, pcbnew, connector rules, and DSN/SES |
references/06-mechanical.md | before declaring a board assemblable; 3D, connectors, folds |
references/07-bringup.md | flashing and first power-up, especially with no USB-serial adapter |
Scripts
scripts/ holds the checkers this workflow depends on. They are deliberately independent
of the EDA: they parse exported documents and Gerbers, so they can contradict the tool that
produced them. Each directory has its own README.
scripts/kicad/— unified 233-command controller (kicad_ctl.py), connector orientation engine (connector_rules.py), pre-flight placement validator (placement_validator.py), post-routing cleanup engine (cleanup_board.py), test suite (run_all_tests.py), deterministic 2-layer layout & routing engine (autoroute_2layer.py), 1-command JLCPCB fabrication & 3D render exporter (export_jlcpcb.py), headless DRC checker with integrated pre-flight audit (drc_check.py), and autorouter runner (route_kicad.py)scripts/placement/— KiCad board importer (import_kicad.py), courtyards from real pads, via-lane widths, module-body clearancescripts/routing/— the DSN/SES autoroute chain with KiCad SES merger (ses_import.py --format kicad), four-state watchdog, and rate floorscripts/verify/— netlist assertions, Gerber parsing, drill census, 3D interferencescripts/notify/— a progress relay so a long run is never silent
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.

