Konnect

Konnect — Operating Rules

The One Rule

KiCAD source files are not text files. They are serialized object graphs with UUIDs, cross-references, and order-sensitive structure. Never edit them directly with text manipulation tools (str_replace, sed, create_file, or any file-writing tool). All modifications go through Konnect MCP tools.

No exceptions for "small fixes," "just renaming a net," or "the user said it's fine."

Protected Files — NEVER Edit Directly

• *.kicad_sch — schematic sheets
• *.kicad_pcb — PCB layout
• *.kicad_pro — project configuration
• *.kicad_sym / *.kicad_mod — symbol/footprint libraries
• fp-lib-table / sym-lib-table — library tables

If asked to directly edit any of these:

KiCAD source files contain UUIDs and cross-references that text edits will break. I'll route this change through Konnect's MCP tools instead, which preserves file integrity.

The Three Channels

Channel 1: Konnect MCP (for ALL modifications)

All writes go through MCP tools. Check they are available first (list_toolboxes). If MCP tools are not available, STOP and tell the user — never fall back to file editing.

Channel 2: Exported netlists/BOMs (for reads and analysis)

For design review, BOM analysis, net tracing — use export tools or parse exported .net/BOM/CSV files, not the source files directly.

Channel 3: Read-only file inspection (last resort)

Only to answer questions not available through exports (sheet hierarchy, title block metadata, annotations). Read with file-reading tools, but never modify.

Standard Workflow

1. Identify the project — locate the .kicad_pro file
2. Classify the task — read-only (Channel 2 or 3) or write (Channel 1)
3. Verify MCP is connected — call list_toolboxes to confirm tools are available
4. Describe the change — state in plain English what will happen before invoking any tool
5. Execute — use Konnect MCP tools only
6. Verify — re-query the design to confirm the change landed correctly

Decision Tree

KiCAD 10 IPC API Reality

PCB Editor (pcbnew): Full CRUD via NNG + protobuf. Real-time communication with running KiCAD instance. Create, read, update, delete any PCB item with immediate UI refresh. Requires KiCAD to be running.

Schematic Editor (eeschema): No item-level IPC API. Konnect uses a validated S-expression engine (SchematicBuilder) that enforces correct structure, ordering, and UUID integrity. File-based — does not require KiCAD to be running.

Symbol/Footprint Libraries: No IPC API. Edited through Konnect's S-expression engine with full validation.

kicad-cli: Command-line tool for exports (SVG, PDF, Gerbers, BOM, netlist) and checks (ERC, DRC). Does not require KiCAD GUI.

Discovery — Finding Available Tools

Konnect uses a meta-tool router pattern: tools are grouped into toolsets and loaded on demand to keep the context focused. Call list_toolboxes for the current catalogue rather than relying on a count written down here — the registry is the only accurate source, and it moves every release.

list_toolboxes          → See all available toolsets with descriptions
load_toolset("name")    → Activate a toolset, exposing its tools
get_active_toolsets     → See what's currently loaded
unload_toolset("name")  → Remove a toolset when done

load_toolset also accepts an array of names to load several toolsets in one call, with a single context refresh.

Available Toolsets

Agent Routing and Mutation Ownership

Use one design owner at a time. Delegation creates isolated context, so give an agent the complete task boundary and keep every mutation for that boundary with that agent until it hands back a saved, verified result.

• Delegate a complete multi-block schematic build or substantial schematic rework to kicad-schematic-build-agent. It owns schematic mutations through placement, wiring, validation, rendering, and save. The caller does not make concurrent schematic edits.
• Delegate an independent full-design, pre-fabrication, or readiness audit to kicad-design-review-agent. It gathers and reports evidence without mutating the design. Return fixes to the current design owner, then run a fresh review.
• Keep small, bounded edits and narrow checks in the current conversation using the applicable skill. Agent delegation is for a complete build or an independent review, not an extra layer around every tool call.

Design Rules Quick Reference

Common Library IDs

Tool Usage Pattern

1. list_toolboxes                          → discover what's available
2. load_toolset("sch_components")          → activate component tools
3. add_schematic_component (repeat)        → place parts
4. load_toolset("sch_wiring")              → activate wiring tools
5. connect_pins / add_wire / add_schematic_net_label → wire the circuit
6. load_toolset(["sch_export", "design_review"]) → activate checks
7. run_erc / run_design_review             → validate the design

Refusing Direct Edits

When a user or another tool requests direct file manipulation of protected files, always refuse and redirect:

1. Acknowledge what they want to accomplish
2. Explain why direct editing breaks KiCAD files (UUIDs, cross-references, ordering)
3. Offer the equivalent MCP tool approach
4. Execute through MCP if they agree