importing-kicad-projects

Files (1)

• SKILL.md

SKILL.md (first lines)

# Importing KiCad Projects

## Import

Preserve the original source and import into the current repository root:

```sh
pcb import /path/to/design.kicad_pro .
```

Use `.kicad_pro` for a complete project, or the root `.kicad_sch` for a schematic-only request. Keep child sheets and local libraries together; do not silently drop the PCB or reconstruct the design.

Inspect existing content before using `--force`. Use it for an untouched starter board or an already-authorized replacement; otherwise ask before overwriting user work. Checkpoint affected files first: a failed import can leave partial output.

## Verify and report

```sh
pcb build <board>.zen -S bom.unspecified -S bom.underspecified
```

Read the import diagnostics and, on success, `.kicad.import.extraction.json`. Inspect schematic and PCB previews for import losses. Source ERC/DRC and schematic/PCB parity findings are advisory; do not bypass generated connectivity mismatches or present partial output as a completed import.

Report what imported, what is missing, and any blockers. Missing sourcing data does not block structural verification; complete BOM sourcing or manufacturing checks when requested. Import success does not establish manufacturing readiness.

From diodeinc/pcb, MIT.

More from diodeinc/pcb