analog-extraction-resim

Extracts parasitic RC from Magic layouts and re-simulates analog blocks across PVT corners.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After analog layout, parasitic resistance and capacitance can silently degrade circuit performance, and a flawed extraction recipe can produce a parasitic-free netlist that makes pre-vs-post comparison report a false 0% degradation. This Skill performs post-layout parasitic extraction and re-simulation, then deterministically compares pre-layout vs post-layout specs to catch layout-induced regressions before tape-out. ## Core Features & Use Cases - Deterministic extraction recipe generation: Emits and validates the Magic parasitic-RC TCL via programs/magic_extract_spice_emit.py, enforcing correct command ordering (extract all, extresist, ext2spice) that Magic 8.3 requires. - Netlist audit before re-simulation: Verifies the extracted SPICE netlist actually contains R/C elements, distinguishing full RC from C_ONLY depth and failing honestly when extraction produced nothing. - Pre-vs-post comparison gate: Runs analog_pre_vs_post_layout_check.py to compute per-metric per-corner degradation against canonical thresholds (≤20% OK, >20% WARNING, >30% NEEDS_RELAYOUT). - Use Case: After finishing Magic layout of an LDO, ask whether the layout hurt bandwidth; the Skill extracts parasitics, re-simulates all PVT corners, and reports that UGB dropped 33%, routing the block back to layout. ## Quick Start Run post-layout extraction and re-simulation on my analog block and tell me whether the layout degraded any specs compared to the pre-layout corner results.

Frequently Asked Questions about analog-extraction-resim

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

FAQPage Schema
How do I run post-layout parasitic extraction and re-simulation on an analog block?▼

Generate the Magic extraction TCL with programs/magic_extract_spice_emit.py, run it to produce an extracted SPICE netlist, re-simulate across the same PVT corners as pre-layout, then run analog_pre_vs_post_layout_check.py to compute per-metric degradation.

Why does my pre-vs-post comparison show 0% degradation after layout?▼

A 0% result usually means the extracted netlist contains no parasitic R or C, so the re-simulation just repeated the pre-layout circuit. Audit the netlist with the --audit-netlist flag; Magic 8.3 resets thresholds if the TCL recipe orders commands incorrectly.

What degradation threshold triggers a relayout for analog blocks?▼

The checker program analog_pre_vs_post_layout_check.py owns the canonical bands: degradation up to 20% is OK, above 20% is a WARNING, and above 30% is an ERROR classified as NEEDS_RELAYOUT, sending the block back to the layout step.

Does the extraction work with both sky130 and gf180 PDKs?▼

Yes, the Skill supports the gf180 and sky130 PDKs. Note that Magic 8.3 with sky130A commonly emits capacitance-only extraction with no R elements, which is passable but must be disclosed as C_ONLY in the result provenance.

What inputs are required before running post-layout resimulation?▼

You need the Magic layout file layout.mag, the pre-layout corner_results.json as the baseline, and the block's spec.json for pass/fail comparison. These come from the earlier analog layout and pre-layout simulation steps.