Choose and implement the grounding strategy of a DipTrace PCB — continuous polygon vs star tie vs islands — from datasheet evidence, and build it headless with pours, stitching vias and thermal reliefs. Use when starting a PCB layout, placing a switching regulator or QFN part, or reviewing a ground system.
Create or edit readable DipTrace schematics and multi-sheet overview diagrams while preserving verified library parts, page containment, and clear human-oriented wiring. Use for schematic authoring or visual cleanup, not read-only electrical review.
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find…
Harvest every ponytail: comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or…
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this…
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports…
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.
Project-authored guidance for DipTrace XML parser, writer, review and evidence work; preserve unknowns and separate synthetic observations from live evidence.
Plan and optionally commit one bounded critical-net or differential-pair route in DipTrace with explicit rules and post-checks. Use when the user says “Route this explicitly named critical PCB net.”.
Collect reviewable DipTrace evidence with native headless PCB acceptance when supported, otherwise guide a human operator through quarantined source/open-save/re-export capture, dry-run ingest, MCP validation, explicit confirmation, and metadata recording. Use when the user says “Guide an operator through a reviewable…
Audit DipTrace component and pattern libraries for pin, pad, mapping, geometry, and identity defects without mutating native libraries. Use when the user says “Audit these DipTrace component and pattern libraries.”.
Inventory a bounded DipTrace project, its document identity, models, rules, connectivity, unknowns, and evidence before planning changes. Use when the user says “Inventory this DipTrace project before we plan work.”.
Produce an explicit evidence-based PASS or BLOCKED decision from implemented DipTrace review profiles and disclosed missing checks. Use when the user says “Run the final evidence-based release gate for this design.”.
Review a DipTrace schematic with bounded ERC, logical connectivity, metadata, and BOM checks before layout. Use when the user says “Review this DipTrace schematic before layout.”.
Review DipTrace PCB impedance, stackup, routed geometry, return paths, and configured external-solver evidence without inventing targets. Use when the user says “Review impedance and return-path evidence for these PCB nets.”.
Measure and improve explicit standalone-pad testpoint coverage through a guarded DipTrace PCB transaction. Use when the user says “Plan guarded fixture testpoints for these PCB nets.”.