pcb-layout-design skill
A Codex skill that guides KiCad component placement, routing and copper pours and prepares the board for ordering
- 170 ★ on the repository
- Last commit
Extended access
Why this level
- The agent may edit KiCad board files, so work on a copy or under version control
Install
- Works in
Manual install
Copy the whole pcb-layout-design folder into the Codex skills directory. First only read the KiCad project: board, version, rules, outline, mounts, stackup and missing inputs. Edit only after the user states the scope and allows changes.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent may edit KiCad board files, so work on a copy or under version control
This is third-party code. Review the repository files before installing.
What it does
pcb-layout-design starts after the schematic and footprint assignment are done. The agent takes the current KiCad project and performs one of five tasks: take the board to completion, only place components, continue routing or tune one area, run a review with no edits, or prepare the board for manufacturing. A rule keeps existing placement, locked objects and mechanical constraints intact. The main `SKILL.md` sets the workflow: identify the project, read the board rules, check the inputs and only then apply the rules. Details live in `references/` notes that the agent reads selectively: layout and mechanics, stackup and return paths, signals and interfaces, routing geometry and crosstalk, manufacturing and KiCad rules, and review checklists. Named interfaces include DDR, USB, CAN and ESD discharge paths. A worked K230D board example sits alongside, with the layout described in `layout_inventory.json`. The README gives sample prompts for each task and asks you to state the fab, the stackup, baseline constraints and permission to modify the project.
Who it is for. Hardware and embedded engineers who let Codex handle board layout and routing in KiCad under their supervision.
Good fit when
- The schematic is final and Codex must place the components while keeping the approved outline, connectors and mounting holes
- Routing and copper pours continue with a check after each group of critical nets
- Before the board goes to the fab you run a separate review with no edits and findings ranked by severity
- A board with DDR or USB where stackup, return path and ESD discharge rules matter
- The K230D board design is studied through a ready breakdown
Not a fit when
- There is no schematic or assigned footprints: the skill does not draw schematics or assign footprints in bulk
- The work is outside KiCad: the notes cover general rules plus KiCad, and other CAD tools need your own check
- You need exact fab tolerances: take them from the specific manufacturer documentation, not from the example
Example request
Read pcb-layout-design/SKILL.md and check the current KiCad project for what is missing before layout. Report only, do not modify the boardLimitations
All skill and README text is in Chinese, and the notes point to Chinese manufacturers such as JLC. Parameters from the K230D example must not be carried over to a new board as rules, and the author asks you to check tolerances and process against official data. Installation is described for Codex: copy the `pcb-layout-design` folder into `~/.codex/skills`, or `%USERPROFILE%\.codex\skills` on Windows. In other agents you must give the `SKILL.md` path in the prompt. DRC and unconnected-net checks are done by KiCad itself and the skill does not replace them.
How to disable. Delete the `pcb-layout-design` folder from the Codex skills directory and restart the session. The skill does not change the KiCad project without your permission, so roll back through your board version control.
FAQ
How do I install pcb-layout-design in Codex?
Copy the whole folder, with `SKILL.md` and `references/`, to `~/.codex/skills/pcb-layout-design`. Restart the session, then call `$pcb-layout-design` or give the `SKILL.md` path in the prompt.
Which CAD tool does the skill work with?
The main workflow is built around KiCad, and one reference describes its rules and checks. The general layout, stackup and signal sections also fit other tools, but tolerances need manual checking.
What should a board edit request include?
The goal, scope, what must stay (outline, connectors, holes, stackup), fab conditions and permission to move components. Unknown items are marked as needing confirmation.
Can I run only a review?
Yes. The review prompt template asks for constraints, missing inputs and problems with no project changes. Findings come ranked by severity with a basis and a suggestion.
What is the K230D example in the repository?
A breakdown of the Lushan Pi Lite K230D board: `k230d-case-study.md` and the layout inventory `layout_inventory.json`. It is training material and does not serve as rules for other boards.
Discussion
No questions or reviews yet.
Related
SkillsA skill that walks an agent from a hardware idea to a PCB, verifies routing and stops before the order is paid.
Skills for coding agents that analyze KiCad schematics and boards, catch design mistakes and prepare boards for fabrication
Eight skills for Codex and Claude Code take an electronics project from schematic to a board order, checking each stage.
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
Four plugins for Claude Code and Codex take a KiCad 10 board from schematic to a JLCPCB order and production-file checks.
Diode's CLI for circuit boards written in Zener: builds a schematic from code, manages dependencies and generates KiCad layout files, with five skills
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| pcb-layout-design (this card) | no | 170 | |
| PCB skill | no | 181 | takes an idea to a board and stops before payment, while this works from a finished schematic: layout, routing and copper |
| kicad-happy | no | 1,648 | analyzes schematics and boards for design errors, while this performs the layout and routing itself |
README in short
The README explains the skill folder layout, three launch steps using an absolute `SKILL.md` path and a request template with goal, scope, fixed items and fab conditions. A table of sample prompts covers the five tasks, followed by installation into the Codex directory and a file navigation list.