KiCad workflow

Preserve .kicad_pro, .kicad_sch, and .kicad_pcb as project source, including custom libraries, rules, placements, and unrelated user work. Use structured operations and real KiCad validation. CAD checks do not prove electrical performance or safety.

Environment and scope

Reuse the project's verified installation and environment. Confirm its executable version and required subcommand capabilities with --help; do not infer them from filenames. Respect a user-selected version. If no installation is recorded, check project setup and PATH first. Read installation discovery when these fail, capabilities are missing, or the user requests the newest local version. Record a working path and version once for reuse.

Inspect the files, library tables, design rules, net classes, stack-up, and existing scripts relevant to the operation. Prefer project jobsets for repeatable exports when they match the request.

Use electronics-design when available for component selection, circuit changes, placement/routing strategy, or fabrication engineering review. An export, render, or file conversion does not require a new engineering review. If the companion is unavailable, establish necessary engineering inputs from requirements and authoritative component documentation before changing the design.

Read only the needed procedure