diptrace
01MCP server Claude CodeCodexCursor +2
MCP server "diptrace" as configured in fireostendere/mcpdiptrace. Launched with C:\path\to\mcp_diptrace\.venv\Scripts\diptrace-mcp.exe. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
MCP server "diptrace" as configured in fireostendere/mcpdiptrace. Launched with C:\path\to\mcp_diptrace\.venv\Scripts\diptrace-mcp.exe. Needs 1 environment variable to run.
Skill Claude CodeCodex
Project-authored guidance for DipTrace XML parser, writer, review and evidence work; preserve unknowns and separate synthetic observations from live evidence.
Skill Claude CodeCodex
A controlled routing workflow for one named critical circuit connection or differential pair in DipTrace, a PCB design program. It uses bounded 45-degree pathfinding and checks the board before and after routing.
Skill Claude CodeCodex
RAG-backed. Collect reviewable DipTrace evidence with native headless PCB acceptance when supported, open/save/close for all four editors and supported native capture; for unsupported actions guide an operator through quarantined source/open-save/re-export capture, dry-run ingest, MCP validation, explicit…
Skill Claude CodeCodex
A read-only checker for DipTrace component and pattern libraries. DipTrace is electronics-design software; these libraries store parts, footprints, pins, pads, and related drawing data.
Skill Claude CodeCodex
A read-only intake process for DipTrace electronics projects. DipTrace is software for designing circuit boards, schematics, components, and connection layouts.
Skill Claude CodeCodex
An evidence-based release check for DipTrace circuit designs. It reviews either a schematic or a PCB against the applicable checks and returns PASS or BLOCKED for the exact file version and review scope.
Skill Claude CodeCodex
A read-only review workflow for DipTrace schematics, which are electronic circuit drawings. It checks electrical rules, connections, component details, and the bill of materials before board layout.
Skill Claude CodeCodex
A review workflow for checking PCB signal quality, including trace shape, board layers, return paths, and available simulation evidence.
Skill Claude CodeCodex
A planning workflow for adding standalone test pads to a PCB, a circuit board, so a fixture can probe selected electrical connections.
Skill Claude CodeCodex
A workflow for planning or guiding the first power-on and functional testing of a specific assembled PCB revision. Board bring-up means applying power carefully, programming the board, measuring signals, and checking whether it works as intended.
Skill Claude CodeCodex
A workflow for building and checking a purchasable bill of materials (BOM) for a DipTrace assembly. A BOM lists the exact parts, quantities, packages, suppliers, and variants needed to build a board.
Skill Claude CodeCodex
A workflow for turning official component datasheets into project rules for DipTrace schematics and PCB layouts. A datasheet is the manufacturer's document describing a part's pins, limits, package, and usage requirements.
Skill Claude CodeCodex
A workflow for preparing and inspecting a versioned manufacturing package for a DipTrace board. It brings together fabrication files such as Gerbers and drill files, assembly data, a bill of materials, instructions, and release evidence.
Skill Claude CodeCodex
A workflow for comparing two DipTrace board revisions and recording their electrical, component, and layout changes in an engineering change order (ECO). An ECO is a controlled record of what changed and what must be rechecked.
Skill Claude CodeCodex
A complete workflow for designing a printed circuit board (PCB) in DipTrace, from requirements and evidence through schematics, layout, manufacturing files, first power-on, and revisions. It uses a shared evidence library and project rules to guide each stage.
Skill Claude CodeCodex
An engineering workflow for designing, editing, and reviewing electronic schematics in DipTrace using documented circuit decisions. A schematic is the diagram that shows components and their electrical connections before a physical board is made.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: