Sim Plugin Ltspice — AI skill for Claude Code

sim-plugin-ltspice

Use Codex, Claude Code, or another AI agent to create, run, debug, and inspect LTspice circuits.

`sim-plugin-ltspice` gives agents a structured path for LTspice work: read or generate `.asc` schematics and `.net`/`.cir` netlists, run LTspice, parse `.log` and `.raw` artifacts, extract `.meas` values, and turn simulation output into grounded engineering reports.

LTspice itself is not bundled. This plugin supplies the agent-friendly file-format, run, and result-inspection layer around the LTspice tools you provide.

What an agent can do with LTspice

• Generate or edit simple SPICE netlists for parameter sweeps and quick checks.
• Convert supported .asc schematics into runnable netlists when the platform supports it.
• Launch LTspice batch runs through the sim CLI or a direct LTspice command.
• Parse .log files for warnings, errors, and .meas outputs.
• Parse .raw waveforms for post-processing and KPI extraction.
• Debug failed runs using verifiable artifacts instead of guessing from a screenshot or a final answer.

The value is not just starting LTspice. The value is making the full circuit-authoring → run → debug → measurement-extraction loop legible to an AI agent and auditable by an engineer.

Common workflows

1. Run a circuit and collect structured results

uv run sim run --solver ltspice path/to/design.net --json

Use this when the agent should keep a structured run record and surface stable errors/results through the sim runtime.

2. Inspect completed LTspice artifacts

Use the bundled Python library when a task already produced `.log` or `.raw` files and the agent needs to extract values without re-running the solver:

python - <<'PY'
from sim_plugin_ltspice.lib import RawRead, parse_log

log = parse_log("design.log")
print(log.measures)

raw = RawRead("design.raw")
print(raw.trace_names())
PY

3. Ask an agent to work on an LTspice task

Give Codex, Claude Code, or another coding