메뉴
Inspect and automate KiCad projects from Pi. Use for schematic/PCB queries, DRC/ERC, fabrication outputs, plots, 3D model export, footprints, symbols, and KiCad IPC or kicad-cli workflows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Design electronic schematics and PCB netlists from Pi using SKiDL. Use for circuit creation, KiCad library parts, nets/buses, ERC, BOMs, SVG schematics, KiCad schematic export, and standalone SKiDL Python.
CAD modeling with build123d from Pi. Use when creating, inspecting, rendering, or exporting parametric 3D models, STL files, STEP files, enclosures, brackets, and other mechanical parts.
Schedule one-time or recurring agent jobs from Pi. Use when the user asks for cron-like reminders, recurring checks, scheduled prompts, or inspecting/completing scheduled jobs.
Track and manage issues using the dude MCP server. List, create, update issues. Track bugs, tasks, blockers, and problems within projects. Search for issues. Use when tracking bugs, creating tasks, managing blockers, recording problems, or working with issue hierarchies.
Manage development projects using the dude MCP server. List projects, view records by project, search across projects. Projects are auto-detected from git — no manual creation needed. Use when exploring project organization, starting work on a codebase, or needing project-level context.
Interactive issue review and grooming session. Pulls all issues for the current project and walks through them with the user to triage, update, resolve, or archive. Use when grooming a backlog, reviewing open issues, or cleaning up stale tasks.
| name | kicad |
| description | Inspect and automate KiCad projects from Pi. Use for schematic/PCB queries, DRC/ERC, fabrication outputs, plots, 3D model export, footprints, symbols, and KiCad IPC or kicad-cli workflows. |
Use kicad_* Pi tools exposed by this package. They bridge the upstream KiCad MCP server.
KICAD_PATH when your platform requires it.Ask before modifying schematic/board files, libraries, footprints, or project settings. Prefer query/validation tools before edits. Run DRC/ERC after generated changes when possible.
Detailed upstream notes are bundled under docs/ and README.upstream.md.