ltspice

Name: ltspice
Author: Power-Agent

56stars12forks

How to install ltspice?

power-agent/powerskills/ltspice

$npx -y skills add Power-Agent/PowerSkills --skill ltspice

Installs into the current project.

Summary

Progressive-disclosure workflow for LTSpice / PyLTSpice circuit simulation. Use whenever the user wants to create a netlist, run a SPICE transient or AC simulation, inspect traces, or debug LTSpice convergence through PowerMCP — even when they just say "simulate this circuit", "w

Files · 1

View on GitHub

SKILL.md

1	# LTSpice workflow
2
3	Start with a runnable netlist and a clean batch simulation. Use plotting and GUI steps only after the run succeeds.
4
5	## Default tool ladder
6	1. `create_rc_transient_netlist(...)` for a minimal example, or `create_simulation_session(netlist_text)` for a real case.
7	2. `run_simulation(netlist_path, session_dir)` to generate the raw and log files.
8	3. `read_simulation_log(log_file_path)` if the run fails or looks suspicious.
9	4. `list_available_traces(raw_file_path)` before requesting plots.
10	5. `plot_specific_traces(raw_file_path, session_dir, trace_names)` for focused waveform review.
11	6. `view_netlist_in_ltspice(netlist_path)` only when the GUI is actually needed.
12
13	## Working rules
14	- Do not ask for broad plotting until the log is clean and the available traces are known.
15	- Simplify the netlist and shorten the run before tuning tolerances.
16	- Use a minimal reproducible circuit to debug startup or convergence issues.
17
18	## Deliver
19	- The netlist used and whether the batch run succeeded.
20	- The traces inspected.
21	- The likely root cause if the simulation misbehaved.

People who liked this also viewed

6 picks

Type

ltspice

56stars12forks

View on GitHub

How to install ltspice?

power-agent/powerskills/ltspice

$npx -y skills add Power-Agent/PowerSkills --skill ltspice

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# LTSpice workflow
2
3	Start with a runnable netlist and a clean batch simulation. Use plotting and GUI steps only after the run succeeds.
4
5	## Default tool ladder
6	1. `create_rc_transient_netlist(...)` for a minimal example, or `create_simulation_session(netlist_text)` for a real case.
7	2. `run_simulation(netlist_path, session_dir)` to generate the raw and log files.
8	3. `read_simulation_log(log_file_path)` if the run fails or looks suspicious.
9	4. `list_available_traces(raw_file_path)` before requesting plots.
10	5. `plot_specific_traces(raw_file_path, session_dir, trace_names)` for focused waveform review.
11	6. `view_netlist_in_ltspice(netlist_path)` only when the GUI is actually needed.
12
13	## Working rules
14	- Do not ask for broad plotting until the log is clean and the available traces are known.
15	- Simplify the netlist and shorten the run before tuning tolerances.
16	- Use a minimal reproducible circuit to debug startup or convergence issues.
17
18	## Deliver
19	- The netlist used and whether the batch run succeeded.
20	- The traces inspected.
21	- The likely root cause if the simulation misbehaved.

People who liked this also viewed

6 picks

Type