Konnect
Mandatory operating rules for ANY task involving KiCAD projects.
Install
npx skills add mixelpixx/Konnect --skill konnect -g -a claude-code -y- Repository
- mixelpixx/Konnect1.4k
- Category
- AI and agents
- Updated
- 3d ago
- License
- AGPL-3.0
- Context cost
- Mediumabout 2,010 tokens
- Runs scripts
- No, instructions only
What it does
Mandatory operating rules for ANY task involving KiCAD projects. Loaded when the user mentions KiCAD, schematics, PCBs, or any .kicad_* file. Prevents file corruption by routing all changes through Konnect MCP tools.
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 librariesfp-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
Before a mutation, a dependent check, a retry, or a completion claim, read the reliability contract, starting with "For callers: establish what happened". Apply its outcome, source, coverage and recovery rules to the fields this installed server actually returns. Guidance does not establish that a missing server-side check ran.

