kicad-mcp-pcb-design
Installation
SKILL.md
KiCad MCP PCB Design
Use this skill when an agent must control KiCad, research components, clone an existing PCB style, produce a new board, and prove the result with KiCad-native validation artifacts.
Core Rules
- Treat PCB output as an engineering draft until a human verifies electrical, thermal, and mechanical constraints.
- Save source-backed component assumptions in a dataset file, including URLs, model numbers, dimensions, currents, voltages, thermal notes, and uncertainty.
- Prefer KiCad-native tooling for validation:
kicad-cli pcb drc,export step,export gerbers,export drill, andrender. - Use
/usr/bin/python3or a venv made with--system-site-packageswhen Python code needspcbnew; Conda Python usually cannot import KiCad bindings. - Stage only intended generated PCB files. Do not accidentally commit large unrelated PCB archives, extracted vendor zips,
__MACOSX/,.DS_Store,fp-info-cache, or local.kicad_prlUI-state files. - For research hardware, document the future system intent separately from the immediate board so assumptions do not get buried inside fabrication files.
Setup
Check KiCad first: