Show HN: Spice simulation → oscilloscope → verification with Claude Code

Hit this exact wall six months back building Claude Code stuff for KiCad review[1]. First pass let Claude read .kicad_sch directly via grep/read. It happily invented pin numbers that didn't exist. Rewrote it with Python analyzers that spit out JSON, now Claude just reads the JSON, problem mostly went away.

Curious how spicelib-mcp handles models that aren't in the bundled library. Do you pass the .lib path as a tool arg, or does the server own a registry?

[1] https://github.com/aklofas/kicad-happy

Beware. I had Claude code with opus building boards and using spice simulations. It completely hallucinated the capabilities of the board and made some pretty crazy claims like I had just stumbled onto the secret hardware billion dollar project that every home needed.

None of the boards worked and I had to just do the project in codex. Opus seemed too busy congratulating itself to realize it produced gibberish.

I've found that having LLMs work with mermaid diagrams makes describing and modifying circuits less annoying.

Measure with a micrometer, mark with a pencil, cut with an axe.

Nice! Doing something similar with a Jumperless so that the model can reconfigure the circuit on the fly.

Very cool idea closing the loop between simulation and real hardware.

Have you found the MCP-driven workflow reliable enough for repeated testing cycles, or does it still need manual verification at key steps?