Hey HN, just sharing some tools that might be useful for you if you design with electronics.
I've found the most annoying and time consuming parts in designing electronics to be:
1. sourcing parts & loading them into my schematic
2. finding semantic errors (like mislabeled nets) that the
traces is my own solution to both:
1. ground sourcing queries via LCSC/Mouser/Digikey MCP
2. have a skill that can look at your schematic and find typos and bugs that a normal rule check simply can't check
the kicad extension is super nice because you can search a part, then save its values (like mpn, price, qty available, datasheet!) directly to the schematic. the schematic should be the ground truth.
this is possible from a few:
- local agents like claude code
- kicad running locally
- kicad files being plain text
Let me know if you have any feedback or future additions that might be useful here!
Hey HN, just sharing some tools that might be useful for you if you design with electronics.
I've found the most annoying and time consuming parts in designing electronics to be: 1. sourcing parts & loading them into my schematic 2. finding semantic errors (like mislabeled nets) that the
traces is my own solution to both: 1. ground sourcing queries via LCSC/Mouser/Digikey MCP 2. have a skill that can look at your schematic and find typos and bugs that a normal rule check simply can't check
the kicad extension is super nice because you can search a part, then save its values (like mpn, price, qty available, datasheet!) directly to the schematic. the schematic should be the ground truth.
this is possible from a few: - local agents like claude code - kicad running locally - kicad files being plain text
Let me know if you have any feedback or future additions that might be useful here!