pcb-agent-workflow plugin
Four plugins for Claude Code and Codex take a KiCad 10 board from schematic to a JLCPCB order and production-file checks.
- 79 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Comparison scripts run Python code and read board project files.
- The correspondence skill drafts emails to support, and an optional confirmation hook guards sending through Gmail.
Install
- Works in
Manual install
/plugin marketplace add John-owo/pcb-agent-workflowThen `/plugin install jlc-support@pcb-agent-workflow` or another plugin from the README table.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Comparison scripts run Python code and read board project files.
- The correspondence skill drafts emails to support, and an optional confirmation hook guards sending through Gmail.
This is third-party code. Review the repository files before installing.
What it does
The repository grew from a four-layer GNSS board project, from design and review through quoting, ordering, factory correspondence and approval of production files. It contains documents, a project template and four skills. `jlc-support` handles correspondence with JLCPCB support using six templates and a deadline calculator. `jlc-production-review` aligns factory production files with the original Gerbers layer by layer and checks BOM and CPL. `readable-schematic-layout` makes schematics and layouts readable and proves the circuit did not change. `kicad-enclosure-step` exports a board as STEP for enclosure design. Each skill installs as a separate plugin from a shared Claude Code and Codex marketplace. An optional `jlc-send-guard` hook requires confirmation before a Gmail message is sent.
Who it is for. People who design a PCB in KiCad 10 with Claude Code or Codex and order production from JLCPCB.
Good fit when
- The factory sent production files and they must be compared with the Gerbers before payment.
- You need to write to a JLCPCB engineer about DFM and not miss the approval deadline.
- A schematic is hard to read and must be redrawn without changing nets.
- An enclosure design needs a board model in STEP with all components.
Not a fit when
- The board is not made in KiCad or ordered from JLCPCB: the skills are written for that pair.
- English documentation is required: most guides are in Traditional Chinese.
- The agent must not handle support correspondence without your confirmation of each message.
Example request
Compare the factory production files with the original Gerbers, list differences by layer and show which need a question to JLCPCB.Limitations
Guides, templates and skills are mostly in Traditional Chinese, with English in the README and in JLCPCB message templates. The production-file comparison scripts in `jlc-production-review` need Python 3.12 and pinned packages: `pip install -r scripts/requirements-cam.txt`. The `jlc-send-guard` hook is off by default and works with Claude Code. The skills assist the agent, but ordering, payment and approval of production files are confirmed by a human, and the project started as the experience of a single board.
How to disable. Uninstall plugins with `/plugin uninstall` in Claude Code or remove the skill folders from `~/.claude/skills` and `~/.agents/skills`. The `jlc-send-guard` hook is disabled together with its plugin.
FAQ
How do I install the plugins in Claude Code?
Run `/plugin marketplace add John-owo/pcb-agent-workflow`, then `/plugin install jlc-support@pcb-agent-workflow`. Replace the name after `install` with the plugin you need.
How do I install them in Codex?
With `codex plugin marketplace add John-owo/pcb-agent-workflow` and `codex plugin add jlc-support@pcb-agent-workflow`. The marketplace and `SKILL.md` files are shared with Claude Code.
Can I skip the plugins?
Yes, copy a skill folder into the agent skills directory, for example `mkdir -p ~/.claude/skills && cp -r pcb-agent-workflow/skills/jlc-support ~/.claude/skills/`. For Codex the user directory is `~/.agents/skills`.
What does the `jlc-send-guard` hook do?
It requires your confirmation before Gmail send tools run. The hook is optional, off by default and meant for Claude Code.
Where should a PCB newcomer start?
With `docs/getting-started.md`: it walks from installing KiCad to a JLC order and says for each step what to do, what to delegate to an agent and how to verify.
Discussion
No questions or reviews yet.
Related
PluginsSkills for coding agents that analyze KiCad schematics and boards, catch design mistakes and prepare boards for fabrication
A Codex skill that guides KiCad component placement, routing and copper pours and prepares the board for ordering
Eight skills for Codex and Claude Code take an electronics project from schematic to a board order, checking each stage.
A Claude Code skill for designing PCBs, CAD and firmware as code that writes fab files only after every gate passes
MCP server for PCB design in KiCAD 10: schematic, routing, checks and manufacturing prep through an agent
The kct CLI and a Python library for agents: parse and edit KiCad schematics and PCBs with JSON output, run DRC and ERC without a running KiCad
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| pcb-agent-workflow (this card) | no | 79 | ||
| KiCad MCP Pro | no | not required | 212 | a KiCad MCP server with ERC, DRC and DFM checks; this one covers the JLCPCB ordering process and four separate skills |
| PCB skill | no | 184 | takes a device from idea to board and stops before payment; this one focuses on factory correspondence and production-file review |
README in short
The text lists process documents, the four skills and their purpose, the shared marketplace, installation in Claude Code and Codex, manual copying and the optional email confirmation hook. A newcomer is pointed to the first-board guide.