Menu
Use when starting any conversation involving electronics, KiCad, PCB design, schematic capture, circuit design, or EDA tasks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when placing footprints on a PCB, routing traces, adding vias or copper zones, deciding trace widths, or planning board layout strategy. Also use when the user asks about PCB stackup, ground planes, trace spacing, or component placement on a board.
Use when executing a schematic placement plan (plan mode) or modifying an existing schematic (modification mode).
Use after circuit-design produces a validated BOM (specs/bom.md) to plan exact component placement coordinates and wiring before schematic capture begins. Pure planning — no file modifications.
Use when running ERC or DRC checks, fixing electrical or design rule violations, debugging unconnected nets, resolving "power pin not driven" errors, or preparing a design for manufacturing export. Also use when the user says "my ERC has errors" or "DRC is failing."
Use when designing an electronic circuit from requirements, choosing topology or regulator type, selecting component values, planning protection circuits, or deciding what goes on a board before schematic capture begins. Also use when the user asks "what components do I need" or "how should I power this."
Based on SOC occupation classification
| name | using-kicad |
| description | Use when starting any conversation involving electronics, KiCad, PCB design, schematic capture, circuit design, or EDA tasks. |
EVERY KiCad operation has a corresponding MCP tool. Do NOT claim a tool does not exist without first listing all available tools. Key tools that MUST be used instead of file writes:
add_symbol — create custom symbol definitions in .kicad_sym filescreate_symbol_library — create new .kicad_sym library filescreate_schematic — create new .kicad_sch filescreate_project — create new .kicad_pro project files
If you find yourself thinking "there's no MCP tool for this," you are
wrong. Check the tool list again.
This is not optional. Do not rationalize skipping it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"KiCad/electronics task?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create TodoWrite todo per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond normally" [shape=doublecircle];
"User message received" -> "KiCad/electronics task?";
"KiCad/electronics task?" -> "Invoke Skill tool" [label="yes"];
"KiCad/electronics task?" -> "Respond normally" [label="no"];
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create TodoWrite todo per item" -> "Follow skill exactly";
}
When a skill contains a checklist (items with - [ ]), you MUST create a TodoWrite entry for each item BEFORE starting work. This provides visible progress tracking throughout the design session.
When this skill activates, print exactly:
KiCad design pipeline is active.
Then explore the project (files, git status). Present findings in this structure:
Project: [name] at
[path]Existing work: [list sheets/files found, one per line] Pipeline position: [which phase the project is at based on existing artifacts like specs/bom.md, specs/schematic-plan.md]What would you like to work on?
Do not list the full pipeline. Do not explain what each skill does. Do not add extra commentary beyond this structure. Keep the response under 8 lines.
This plugin enforces a validated pipeline for electronics design. Every phase produces evidence before the next phase can start.
circuit-design ---- requirements -> validated BOM artifact
|
| EXIT GATE: resolve all lib_ids + footprints, write specs/bom.md
| BOM reviewer subagent validates artifact
| HARD GATE: user approves BOM
|
v
schematic-plan ---- BOM -> placement & wiring plan artifact
|
| Reads specs/bom.md
| Produces specs/schematic-plan.md with exact coordinates
| Schematic plan reviewer subagent validates artifact
| HARD GATE: user approves plan
|
v
schematic-design -- plan -> mechanical execution
|
| Reads specs/schematic-plan.md, executes mechanically
| EXIT GATE: run ERC, must be zero violations
|
v
verification ------ ERC gate (blocks PCB until clean)
|
| HARD GATE: ERC = 0 violations
|
v
pcb-layout -------- netlist -> board layout
|
| PRE-FLIGHT: verify all footprints exist
| EXIT GATE: run DRC, must be zero violations
|
v
verification ------ DRC gate (blocks export until clean)
|
| HARD GATE: DRC = 0 violations
|
v
Export ------------- Gerbers, drill, BOM, pick-and-place, 3D,
fabrication notes, assembly drawing
What constitutes "user approval": The user explicitly says something like "approved," "looks good," "proceed," "yes," or "go ahead." Asking a question or requesting changes is NOT approval.
| Skill | Invoke as | When to use |
|---|---|---|
| circuit-design | /kicad:circuit-design | Choosing topology, selecting components, calculating values, creating a validated BOM |
| schematic-plan | /kicad:schematic-plan | Planning exact placement coordinates and wiring from a validated BOM |
| schematic-design | /kicad:schematic-design | Executing a placement plan OR modifying an existing schematic |
| pcb-layout | /kicad:pcb-layout | Placing footprints on a PCB, routing traces, adding vias and copper zones |
| verification | /kicad:verification | Running ERC/DRC, fixing violations, preparing for manufacturing export |
list_lib_symbols before placement.| Anti-Pattern | Why It Fails |
|---|---|
| "I know this IC's pinout from memory" | You're recalling training data, not the library. Call get_symbol_info. |
| "The datasheet app circuit is simple enough to place without planning" | That's exactly what produced 9 wasted tool calls in previous failures. |
| "Standard 100nF decoupling is fine" | The datasheet specifies the cap value and ESR. Check the datasheet. |
| "This symbol name is probably right" | Q_PMOS_GSD sounded right. It doesn't exist. Call list_lib_symbols and verify. |
| "A4 is big enough, I'll check later" | Later = after 4 failed placements. Calculate first. |
| "These nets are obvious, I don't need to plan the wiring" | Obvious to you means hallucinated pin names. Query the library. |
| "I'll just use the same component I used last time" | Training data bias. The library may have been updated. Verify. |
| Thought | Reality |
|---|---|
| "I already know the components, skip circuit-design" | You'll hallucinate lib_ids. Do the phase. |
| "The plan is simple enough to do in my head" | That's what caused 9 wasted tool calls last time. Write the plan. |
| "I'll just fix the page size when it fails" | Pre-calculate it. Reactive fixes waste tokens. |
| "ERC will probably pass, start PCB layout" | Run ERC. "Probably" is not evidence. |
| "This is just a small change, no need for the full pipeline" | Small changes use modification mode. But modification mode still validates lib_ids. |
| "The user already validated this, skip the reviewer" | The reviewer checks what humans miss — pin names, coordinate math, spacing. Always run it. |
The KiCad MCP server gives you tools to drive KiCad programmatically. You do not need the user to click anything in KiCad — the tools do it for you. Tool groups (107 tools total):
create_project, create_schematic,
create_symbol_library, create_sym_lib_table,
add_hierarchical_sheet, run_jobset, get_versionadd_symbol (create custom symbol
definitions), list_lib_symbols, get_symbol_info,
export_symbol_svg, upgrade_symbol_libplace_component, move_component,
remove_component, set_component_property, set_page_size,
add_lib_symbolconnect_pins, wire_pins_to_net,
add_wires, add_label, add_global_label, add_junctions,
no_connect_pin, remove_label, remove_wire, remove_junctionadd_power_symbol,
auto_place_decoupling_capget_schematic_summary,
list_schematic_components, list_schematic_labels,
list_schematic_wires, list_schematic_global_labels,
list_schematic_hierarchical_labels, list_schematic_sheets,
list_schematic_junctions, list_schematic_no_connects,
list_schematic_bus_entries, get_symbol_pins,
get_pin_positions, get_net_connections,
list_unconnected_pins, add_textrun_erc, export_schematic,
export_netlist, export_bomannotate_schematic,
validate_hierarchy, add_hierarchical_sheet,
remove_hierarchical_sheet, modify_hierarchical_sheet,
add_sheet_pin, remove_sheet_pin, move_hierarchical_sheet,
list_hierarchy, get_sheet_info, is_root_schematic,
trace_hierarchical_net, list_cross_sheet_nets,
get_symbol_instances, export_hierarchical_netlist,
flatten_hierarchy, duplicate_sheet, reorder_sheet_pages,
remove_text, add_hierarchical_label,
remove_hierarchical_label, modify_hierarchical_labelplace_footprint, move_footprint,
remove_footprintadd_trace, add_via, autoroute_pcb,
set_trace_width, remove_traces, add_thermal_vias,
set_net_class, remove_dangling_tracks, add_copper_zone,
fill_zonesadd_pcb_text, add_pcb_linelist_pcb_footprints, list_pcb_traces,
list_pcb_nets, list_pcb_zones, list_pcb_layers,
list_pcb_graphic_items, get_board_info,
get_footprint_padsrun_drc, export_pcb, export_gerbers,
export_3d, export_positions, export_ipc2581list_lib_footprints,
get_footprint_info, export_footprint_svg,
upgrade_footprint_librun_jobset (batch operations from .kicad_job files),
get_version (KiCad version info), export_symbol_svg,
upgrade_symbol_lib, export_footprint_svg,
upgrade_footprint_libAlways invoke the matching skill for conventions, spacing, and strategy before using these tools.