メニュー
Run external DFM analysis using KiBot (DRC/ERC/design report) and Tracespace (gerber validation) via Docker. Use after internal verify passes to get a second opinion from third-party tools.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Full PCB verification loop using local kicad-cli (DRC + 3D render + gerbers)
Create a new Claude Code skill for this project. Use when you need to add a new skill, improve an existing skill, or convert a workflow into a reusable skill.
Verifies that every PCB pad-to-net assignment matches the manufacturer datasheet pin specifications. Use when changing board.py/routing.py/footprints.py, after GPIO remapping, before releases, or when adding new components. Automated guard against wiring errors like unconnected VBUS, wrong pin assignments, or missing GND connections.
Design intent adversary — cross-checks GPIO, nets, power chains, signal paths across firmware/schematic/PCB/datasheet sources to find lost connections and inconsistencies
Analyze a DFM report and fix all issues in the PCB generation scripts
Run DFM guard tests and add new regression tests after fixing PCB issues
| name | external-dfm |
| model | claude-opus-4-7 |
| description | Run external DFM analysis using KiBot (DRC/ERC/design report) and Tracespace (gerber validation) via Docker. Use after internal verify passes to get a second opinion from third-party tools. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep, Glob |
Run third-party CLI tools in Docker for independent PCB verification — a "second opinion" beyond the internal verify suite.
| Tool | Checks | Output |
|---|---|---|
| KiBot DRC | KiCad native DRC with zone fill | external-dfm-output/esp32-emu-turbo-drc.json |
| KiBot ERC | Electrical rule check on schematics | external-dfm-output/esp32-emu-turbo-erc.json |
| KiBot Report | Full design report (traces, vias, pads, Eurocircuits class) | external-dfm-output/*report*.txt |
| KiBot BOM | Independent BOM generation for cross-check | external-dfm-output/bom-kibot.csv |
| Tracespace | Gerber file parsing and structural validation | external-dfm-output/tracespace.log |
| BOM Cross-ref | Compare KiBot BOM vs JLCPCB BOM designators | Inline in output |
cd /Users/pierrejonnycau/Documents/WORKS/esp32-emu-turbo
bash scripts/external-dfm.sh
This builds the Docker container (first run ~2-3 min, then cached) and runs all checks.
If the script reports issues, inspect the detailed output:
# KiBot DRC violations (JSON)
cat hardware/kicad/external-dfm-output/esp32-emu-turbo-drc.json | python3 -m json.tool
# KiBot ERC violations (JSON)
cat hardware/kicad/external-dfm-output/esp32-emu-turbo-erc.json | python3 -m json.tool
# Full design report
cat hardware/kicad/external-dfm-output/*report*.txt
# KiBot log (full output)
cat hardware/kicad/external-dfm-output/kibot.log
DRC violations — Compare against internal verify_dfm_v2.py results. New violations from KiBot that internal scripts missed are the most valuable findings.
ERC violations — Schematic-level issues (missing connections, power flags, pin conflicts). These are NOT checked by internal scripts.
Design report — Look for:
BOM mismatch — Components present in schematic but missing from JLCPCB BOM (or vice versa).
scripts/external-dfm.sh — Runner scripthardware/kicad/external-dfm.kibot.yaml — KiBot configurationdocker/kibot/Dockerfile — Docker image definitionhardware/kicad/external-dfm-output/ — All output (gitignored)make external-dfm