Live data from Hacker News

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

lucasgerads.com

11–20 of 46 posts

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#12

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…

Spicelib really just makes calls to the selected spice engine (in my case ngspice). In this setup spicelib‘s main job is to parse the raw spice data and have a unified interface regardless which spice engine is selected. But to answer the question: the path to the spice model must currently be set explicitly.

Re: Show HN: SPICE simulation → oscilloscope → verification with Claude Code

#15

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…

[flagged]
Post reply on HN