analog-netlist-gen

Generates SPICE netlists and testbenches from sized analog topologies with PDK device models.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill analog-netlist-gen-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analog-netlist-gen
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/analog-netlist-gen
Command: npx skills add https://github.com/vibeic/vibe-ic --skill analog-netlist-gen-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Converting a sized analog circuit topology into a valid, simulatable SPICE netlist is error-prone: wrong body connections, missing model includes, and mismatched supply voltages are the most common causes of simulation failure. This Skill automates that translation and enforces correctness with deterministic checker programs instead of manual review. ## Core Features & Use Cases - SPICE Netlist Generation: Produces a subcircuit (.sp) and testbench (tb_*.sp) from a sizing table and topology description, with correct GF180 or SKY130 device instantiation. - Deterministic Compliance Gates: Runs checker programs that catch PMOS/NMOS body-connection errors, missing model includes, wrong include order, floating nodes, and supply/PDK mismatches. - Automated .meas Generation: Derives measurement statements directly from spec.json via a generator program rather than hand-authoring them. - Use Case: After sizing a two-stage op-amp for the gf180 PDK, invoke this Skill to emit the subcircuit netlist and a testbench with DC/AC stimulus, then pass it to ngspice simulation at Step A4. ## Quick Start Ask the AI to generate a SPICE netlist and testbench for your sized analog block using the gf180 PDK, then run the compliance gate to verify the output.

Frequently Asked Questions about analog-netlist-gen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a SPICE netlist from an analog sizing table?▼

Provide the topology description, sizing table with W/L values, and spec.json, then this Skill emits a subcircuit .sp file and a tb_*.sp testbench. It instantiates devices with the correct PDK models and generates .meas statements from the spec automatically.

What PDKs are supported for SPICE netlist generation?▼

The Skill supports gf180 (gf180mcuD, 3.3V devices like nfet_03v3/pfet_03v3) and sky130 (sky130A, 1.8V devices like sky130_fd_pr__nfet_01v8). Supply voltage and device flavor are checked against the selected PDK by a deterministic program.

Why does my SPICE simulation fail with body connection errors?▼

The most common failure is connecting a PMOS body to VSS or an NMOS body to VDD. The analog_netlist_pdk_check.py program enforces NMOS body to ground and PMOS body to VDD, failing with PMOS_BODY_TO_VSS or NMOS_BODY_TO_VDD codes.

Can I hand-write .meas statements instead of generating them?▼

No, .meas statements must be generated deterministically from spec.json using analog_meas_from_spec_gen.py, which classifies each spec key into DC, AC, or TRAN measurements. Hand-authoring is explicitly disallowed to avoid errors.

What checks run on the generated SPICE netlist before simulation?▼

Six deterministic gates run: body connections and model includes, include ordering, absolute-path linting, floating-node and unused-port connectivity, supply-PDK matching, and .meas generation. A final compliance check against compliance.yaml must return PASS before handoff.