using-kicadlisted

<CRITICAL-RULE> NEVER use the Read, Write, or Edit tools on KiCad files (.kicad_sch, .kicad_pcb, .kicad_sym, .kicad_mod, .kicad_pro, .kicad_prl). ALL KiCad file manipulation MUST go through the kicad MCP tools. NEVER run kicad-cli commands via Bash. If an MCP tool returns an error, try different parameters — do NOT fall back to manual file editing. 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 files - `create_symbol_library` — create new .kicad_sym library files - `create_schematic` — create new .kicad_sch files - `create_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. </CRITICAL-RULE> <SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> When working on ANY electronics or KiCad task, you MUST follow this pipeline. Do not place components, route traces, run checks, or select parts without first completing prior phases and their gates. This is not optional. Do not rationalize skipping it. </EXTREMELY-IMPORTANT> ## Skill Activation Flow ```dot digraph skill_flow { "User message received" [shape=doublecircle]; "KiCad/electronics task?" [shape=diamond]; "Invoke Skill tool" [shape=box