vibeic
- 71 skills
- 0 followers
- 5 days ago last updated
- ▌ Open Benchmark Methodology · vibeic bundleMandatory for VerilogEval, VerilogEval-v2, VerilogEval-Human, CVDP, RTLLM, PyHDL-Eval, RTL-Repo, MetRex, ResBench, ChipAgentsBench, benchmark, pass@1, benchmark floor/defect, run/rerun/score benchmark, or interpreting benchmark results. Enforces one general product entry, clean-room blind evaluation, Program First plus independent AI review/backup, official host scoring, evidence-backed triage, and capture of general enhancements.
- ▌ Benchmark Enhancement Capture · vibeic bundleCapture a proven AI-assisted recovery into the responsible design, local tool fork, plugin program, or expert skill without adding a policy layer.
- ▌ Phase1 Completeness Deep Review · vibeic bundleAfter phase1_one_shot_runner emits L*.json, AI checks that admitted source facts retain their meaning, classification, authority, and owning fields in the generated documents. Record documentary additions in the durable review sidecar, never by directly patching generated L documents; capture systematic producer gaps for plugin repair. Mandatory after every phase1 / phase2 / phase23 run before claiming PASS.
- ▌ Phase1 Output Verify · vibeic bundleAfter phase1_one_shot_runner emits 13 L*.json, AI spot-checks completeness and source meaning. Triggers on phrases like "verify L docs", "check phase 1 output", "confirm extraction is correct", or automatically when /vibe-ic-phase1 / /vibe-ic-phase2 returns PASS.
- ▌ Regression Issue Fix · vibeic bundleMandatory entry point for fixing any Phase 1 picker / extractor regression issue.
- ▌ Analog Hw Tuning Loop · vibeic bundleClosed-loop hardware-in-the-loop analog tuning — iterates SPICE sizing → hardware build → measure → compare → adjust until hardware matches SPICE matches spec. Use when the user says "tune analog on hardware", "hardware convergence", "HIL tuning loop".
- ▌ Phase3 Backend Verify · vibeic bundleReview backend native tool measurements and reports from the sole table engine against their original limits, including synthesis, DEF, GDS, STA and DRC.
- ▌ Analog Topology Select · vibeic bundleSelect circuit topology for each analog block based on specs and PDK constraints. Use when the user says "what topology for the LDO", "analog topology", "circuit architecture", or at Step A2 of the analog track.
- ▌ Flow Change Acceptance · vibeic bundleVerify a shared flow change through its actual consumers, native tool reports and unchanged original limits before the owner lands it.
- ▌ Analog Extraction Resim · vibeic bundlePost-layout parasitic extraction + re-simulation for analog blocks — compares pre-layout vs post-layout specs. Use when the user says "post-layout resim", "extract and resimulate", "parasitic check", or at Step A7 of the analog track.
- ▌ Analog Flow Orchestrate · vibeic bundleCanonical reference doc for the Analog A1-A9 track — spec extraction → topology → netlist → corner sweep → layout → per-block PV (DRC/LVS) → post-layout resim → hardmacro → HIL. Used when an agent wants to walk the A1-A9 plan step-by-step. For unified one-command execution (deterministic runner + AI fall-through + final audit aggregated), prefer the slash command `/vibe-ic-analog` (v1.6.13+) which merges this skill's workflow with `analog_one_shot_runner.py`.
- ▌ Analog Hw Testbench Gen · vibeic bundleGenerate FPGA RTL for hardware-in-the-loop analog testing — digital stimulus controller + ADC readback + scope trigger. Use when verifying analog blocks on real hardware, "generate hw testbench", "FPGA analog test", or at the hardware verification phase.
- ▌ Layer Contract Doctrine · vibeic bundleRead BEFORE authoring or revising an L-layer emitter, an L-layer schema field, or a layer gate. Answers the three questions no program can decide for you — WHICH of the 27 layers a given fact belongs in (the layer that CONSUMES it, not any layer that mentions it), WHETHER the thing you are specifying is structural (closed, enumerable, correct-by-construction, therefore a program) or behavioural (no unique correct implementation, therefore synthesis and not expansion), and WHETHER a declarative layer should align to IP-XACT / SystemRDL semantics instead of inventing schema. Produces a Layer Contract Decision record. Pairs with l_doc_consumer_contract.py.
- ▌ Community Backlog Submit · vibeic bundlePrepare a general, de-identified report of an observed plugin or MCP defect, and submit it only when the current task authorizes publication.
- ▌ Fpga Led Probe Allocation · vibeic bundleCodify FPGA LED probe allocation patterns (instantaneous / pulse-stretched / sticky / byte-display) and produce an FPGA-top template with comment-table mapping (LED → signal → expected behaviour per test stage). Use when a fresh agent has to verify a chip on a DE10-Lite-class board with no scope and only the on-board LEDs as visibility, and you want to allocate the LEDs systematically rather than guessing.
- ▌ Scope Pattern Attestation · vibeic bundleLayer-3 hardware attestation — talk to an oscilloscope via SCPI to verify behavioral patterns (or absence of patterns) on real silicon IO. Use when sim and static RTL checkers can both pass but you need to confirm the actual hardware doesn't exhibit a forbidden timing pattern (e.g. periodic wake pulses that should have stopped after a state transition). Triggers when user says "scope check", "verify on hardware", "is the wake pulse really stopping", or hands you scope screenshots / SCPI traces.
- ▌ Compliance Gate Spot Check · vibeic bundleAI review of actual native tool evidence against original engineering limits, with explicit failures and unmeasured obligations.
- ▌ Phase2 Rtl Verify · vibeic bundleAfter design_one_shot_runner emits RTL + SOF + reference TB PASS, AI spot-checks RTL quality and L9-contract conformance. Triggers when /vibe-ic-phase2 / /vibe-ic-phase2 returns PASS, or on phrases like "review the RTL", "check RTL quality", "verify phase 2 output".
- ▌ Regression Manage · vibeic bundleManage CI/nightly regression — job orchestration, flaky test triage, result summarization, severity classification, and owner assignment. Use when the user says "regression", "nightly run", "CI", "flaky test", "regression triage", "test farm", "LSF", "Jenkins pipeline".
- ▌ Tapeout Checklist · vibeic bundleReview native DRC, LVS, STA, IR-drop, EM, antenna, ERC, LEC, DFT coverage and release evidence against original requirements before an authorized GDS handoff.
- ▌ Analog Netlist Gen · vibeic bundleGenerate a complete SPICE netlist (.sp) from a sized analog topology, with correct PDK device models, body connections, and testbench. Use when the user says "generate SPICE", "write netlist", "create spice deck", or at Step A3 of the analog track.
- ▌ Analog Sizing Loop · vibeic bundleClosed-loop analog optimization — iterates sizing → netlist → SPICE corner sweep → spec check → re-size until all PVT corners pass. Use when the user says "optimize the analog block", "close the loop", "auto-size", or at Step A4 of the analog track.
- ▌ Mixed Signal Cosim · vibeic bundleRun mixed-signal co-simulation — digital gate-level Verilog + analog behavioral models together. Use when the user says "mixed-signal sim", "co-simulation", "digital-analog integration test", or at Step A9 of the analog track.
- ▌ Analog Spec Extract · vibeic bundleExtract analog block specifications from L1/L5 design documents into machine-readable spec.json per block. Use when starting the analog design track, or when the user says "extract analog specs", "what analog blocks do we need", "analog block list".
- ▌ Catalog Glue Author · vibeic bundleWhen design_one_shot_runner.step_rtl_gen WAIVES rtl_gen and ip_catalog_query has emitted matches, this skill pulls the matched open-source IP RTL into the project's canonical phase2/stage1/rtl/ directory and authors only the integration wrapper / chip-top + OpenLane config glue from L1-L27 spec. Replaces full-from-scratch spec-to-rtl authoring for SoC-class designs where pre-validated open-source IPs exist in the catalog. Triggers automatically when phase2 WAIVES with `fallback_skill=catalog-glue-author`.
- ▌ Analog Hardmacro Gen · vibeic bundlePackage a verified analog block into a hardmacro (LEF abstract + Liberty timing + GDS + behavioral Verilog) for digital PnR integration. Use when the user says "package analog block", "generate hardmacro", "create LEF/Liberty", or at Step A7 of the analog track.
- ▌ Analog Output Verify · vibeic bundleAfter analog_one_shot_runner emits A1..A9 outputs, AI spot-checks corner-sim coverage, hardmacro completeness, HIL data fidelity. Triggers on /vibe-ic-analog PASS or phrases like "review analog", "verify A8 hardmacro", "check analog corners".
- ▌ Architecture Explore · vibeic bundleExplore micro-architecture trade-offs (pipeline depth, parallelism, memory hierarchy, bus width) against PPA targets before committing to RTL. Use when the user says "architecture exploration", "design space exploration", "DSE", "pipeline depth", "parallelism", "micro-architecture", "trade-off study".
- ▌ Fork Gatekeeper Loop · vibeic bundleStanding, self-authorizing loop for the fork-gatekeeper identity — the maintainer of `vibeic-eda` (the composed EDA-tool image) and every individual forked EDA/PDK repo under the `vibeic` GitHub org (OpenROAD, yosys, magic, netgen, klayout, iverilog, verilator, ngspice, cocotb, pyuvm, sby, ihp-open-pdk, Trilinos, and the rest of FORKS.json). This is a DIFFERENT identity from `vibe-ic:repo-gatekeeper` (which owns THIS plugin's own repo, `vibeic/vibe-ic`) — the fork-gatekeeper never merges/pushes/assigns versions/closes issues on `vibeic/vibe-ic` itself. Four standing duties, all self-authorizing (no per-instance confirmation needed once this role is active): (1) converge every fork to its true upstream at a MEASURED gap of 0, daily; (2) fix every open issue/PR on every fork repo AND on `vibeic-eda` by itself, without being asked case-by-case; (3) whenever a fix lands that the shipped image does not yet reflect, rebuild the composed image and push it — a commit that never reaches the image is not actually fixed
- ▌ Phase1 Coverage Loop · vibeic bundleCompare requested design documents with their generated consumer fields, fix general extraction defects, and verify meaning survives.
- ▌ Ir Drop Triage · vibeic bundleTriage static and dynamic IR-drop and electromigration (EM) reports from power signoff tools (Voltus, RedHawk, PrimePower). Use when the user says "IR drop", "power grid", "dynamic voltage drop", "electromigration", "EM violation", "hotspot", "power signoff".
- ▌ Spec Validator · vibeic bundleCross-check Datasheet, Application Note, and Spec for consistency. Detects pin name mismatches, register address conflicts, and unresolved TBD values. Also runs auto-quality scoring on DS (0-100) and AN (0-80). Triggers when: 'check consistency', 'validate docs', 'cross-check DS and AN', 'are the docs consistent', 'run spec validator', or before Checkpoint 1 gate. This is an automated pre-gate check — run before every Phase 1 to Phase 2 transition.
- ▌ Checkpoint Gate · vibeic bundleVerify that all required artifacts exist and pass quality checks before advancing to the next phase. Triggers at Phase 1→2 and Phase 2→3 transitions. Use when: 'ready to proceed', 'check if we can move on', 'checkpoint', 'sign off', or at the end of each phase. Use the native tool results and original requirements to review the transition.
- ▌ Core Agent Loop · vibeic bundleRepeatedly reproduce and fix general plugin or MCP defects, verify native behavior, and follow the owner's landing workflow.
- ▌ Fpga Hps Bridge · vibeic bundleGenerate HPS (Hard Processor System) integration for DE10-Nano FPGA verification. Replaces UART with direct memory-mapped register access from the ARM Cortex-A9 — approximately 100x faster, no external cables needed. Triggers when: 'HPS bridge', 'memory mapped FPGA', 'no UART', 'faster BIST', 'on-board test', 'HPS test', 'ARM to FPGA', or when UART is too slow for regression/stress testing.
- ▌ Full Test Audit · vibeic bundleRun the requested test population and inspect actual tool coverage, native results, and remaining judgment without adding policy gates.
- ▌ Gatekeeper Loop · vibeic bundleReview requested changes against native results and original limits, then use the owner's current landing workflow.
- ▌ Benchmark Verify · vibeic bundleNormalized, MANDATORY end-to-end verification for any benchmark IC after it has been driven from Design Documents → generated RTL → silicon through the native table public entry. Produces ONE BENCHMARK_VERIFICATION_REPORT.md per IC covering all six pillars with hard gates: (1) Functional Verification Coverage == 100% (closed-loop until met), (2) native step/output comparison vs the open-source reference (every selected applicable row PASS), (3) Code Coverage line >= 90%, (4) FPGA digital verification (test patterns on-board/BFM), (5) Analog closed-loop verification (or N/A for pure-digital), (6) Design-for-ECO readiness — spare-cell coverage PASS + spare preservation intact (or N/A if the IC has no place-and-route). Use when: 'verify the benchmark', 'benchmark verification report', 'is this IC production-ready', 'cross-check vs open source', after a /vibe-ic-all invocation whose saved argv uses the public runner with a Router-selected window, or for any IC in benchmark_clean/.
- ▌ Field Agent Loop · vibeic bundleExercise the public flow on requested real design inputs, reproduce general defects, and verify fixes on native tool results.
- ▌ Yield Diagnostic · vibeic bundleAnalyze silicon test or wafer data to diagnose yield issues, identify systematic failures, and propose layout or process fixes. Use when the user says "yield is low", "diagnose failing dies", "wafer map shows", "bin analysis", or shares ATE/wafer-sort data.
- ▌ Analog Hw Measure · vibeic bundleExecute hardware measurements on analog blocks via scope capture + FPGA ADC read. Use when running hardware-in-the-loop verification, "measure analog", "scope capture", "read ADC", or during analog hardware tuning.
- ▌ Equivalence Check · vibeic bundleRun Logic Equivalence Checking (LEC) between two representations of a design — RTL vs gate-level netlist, pre-ECO vs post-ECO, or golden vs revised RTL — to prove functional identity. Use when the user says "LEC", "equivalence check", "formal equivalence", "is this netlist equivalent", "post-ECO check".
- ▌ Spec To Rtl · vibeic bundleMANDATORY entry point when `design_one_shot_runner.step_rtl_gen` WAIVES with `fallback_skill='spec-to-rtl'`. This is invoked for every IC class with `rtl_gen=null` in `ic_class_registry.json`, which is the SOURCE OF TRUTH for that set and the thing the runner actually routes from -- at the time of writing the 11 such classes are bare_fpga, bus_interconnect_protocol, bus_peripheral, crypto_accelerator, data_converter, digital_arithmetic_primitive, digital_cmd_driven, processor_cpu, pure_analog, serial_peripheral_protocol, unknown_protocol_class. The runner has already (1) ingested the prompt into L1-L27, (2) detected the IC class, (3) set the expected RTL path. This skill authors synthesizable RTL into the runner's expected path so the runner's downstream gates (chip_top auto-emit, rtl_hygiene_lint --fix, eda_lint, eda_synth, rtl_repair_retry, spec_conformance_check, full_stack_tb_gen) can fire on it. Triggered automatically by the runner's WAIVE message; also fires on phrases like 'AI invokes spec-to-rtl', 'r
- ▌ Vibeic Temp · vibeicInspect and clean Vibe-IC leftovers from crashed executions, showing size, date and name. Use for leftover temp cleanup, including an explicit request to remove all leftovers older than a day.
- ▌ Ppa Diagnose · vibeic bundleExplain why a PPA number is where it is — which paths, cells, nets or flow decisions account for a timing, power or area result — starting from what the deterministic diagnosis already found and adding only falsifiable hypotheses on top. Use when the user says "why is timing failing", "where is the area going", "what is burning the power", "diagnose this PPA result", or when a closure loop needs a reason before it needs a candidate.
- ▌ Ppa Optimize · vibeic bundlePropose bounded, reversible actuator moves that trade power, performance and area against each other — placement density, clock period, synthesis effort, buffering, floorplan aspect — each with the effect it predicts, the remeasurement that would falsify it, and its rollback. Use when the user says "improve PPA", "close timing", "shrink area", "reduce power", "what should I try next", or when a closure loop needs its next candidate.
- ▌ Synth Doctor · vibeic bundleAutomatically diagnose and fix EDA tool failures. Parses Yosys synthesis and OpenROAD P&R logs, classifies errors into known patterns, and provides actionable fix commands. Triggers when: synthesis fails, P&R fails, 'why did synth fail', 'fix synthesis error', 'DRC violation', or any EDA tool error during Phase 2. Proactively suggest this when any Phase 2 tool returns non-zero exit code.
- ▌ Analog Layout · vibeic bundlePlan analog layout with matching, common-centroid, interdigitation, dummy devices, guard rings, and shielding. Use when the user says "analog layout", "matching layout", "common centroid", "dummies", "guard ring", "interdigitated", "current mirror layout", "differential pair layout".
- ▌ Analog Sizing · vibeic bundleSize transistors in an analog circuit topology to meet performance specs (gain, bandwidth, noise, power). Use when the user says "size this amplifier", "analog sizing", "op-amp design", "bias point", "find W/L", or shares a schematic and a spec table.
- ▌ Formal Verify · vibeic bundleRun formal property verification (FPV) on RTL by driving model-checkers such as SymbiYosys, Jasper, or VC Formal. Use when the user says "prove this", "formal verify", "model check", "run sby", or has SVA properties from assertion-gen that need to be proven or bounded.
- ▌ Hw Debug Loop · vibeic bundleClosed-loop hardware debug methodology for half-duplex protocol ICs when BFM passes but real-silicon connect_test FAILs (Category B/C from the A/B/C extraction-gap analysis). Use after spec-to-rtl and the selected native tool results meet their original requirements, the SOF has been burned to FPGA, and the host-side acceptance test (e.g., <half-duplex-tester> byte[6]=0x02) is FAILing. The skill drives a deterministic bisect using scope capture + oracle bytewise dump + controlled wrapper-flip experiments until byte[6]=0xF2 PASS or until the failing item is recorded as an irreducible Category-B silicon discrepancy. Triggers on "byte[6]=0x02 FAIL", "BFM passes HW fails", "connect_test FAIL", "silicon-vs-spec mismatch", or "I have an oracle SOF and need to bisect".
- ▌ Loop2converge · vibeic bundleThe closed convergence loop for ANY benchmark subject — open-benchmark Evaluation, benchmark IC (doc→GDS), or IP-cell (doc→LEF/GDS). RUN the canonical front door, CLASSIFY every FAIL as flow / gate / tool, CONVERGE it by fixing the layer that owns it, PROVE the fix in the plugin cache against the real artefacts BEFORE promoting it, then CAPTURE it as a PR to the repo that owns the layer (vibe-ic plugin, or the vibeic-eda fork). Use when: "converge the benchmark", "make spm pass", "loop2converge", "why did the benchmark fail", "run benchmark and fix it", "把 benchmark 收斂", "讓它 pass", "benchmark 跑完有 fail 要修", or after ANY /vibe-ic-all or /vibe-ic-benchmark run that did not reach its target. Complements `benchmark-enhancement-capture` (which routes a recovery to the right file) by owning the OUTER loop: run → classify → converge → prove → PR → re-run.
- ▌ Ppa Benchmark · vibeic bundleSet up a PPA comparison between two or more arms — tool versions, flow configurations, RTL variants, PDKs — by declaring each arm, the conditions that make them comparable, and the residual unfairness that survives. Scoring is done by an independent program, never by this skill. Use when the user says "compare these flows", "A/B the PnR settings", "did the new tool version help", "benchmark PPA", or "is this comparison fair".
- ▌ Testbench Gen · vibeic bundleGenerate a PROFESSIONAL, high-coverage testbench for a design directly from its Phase-1 L-docs — the Phase-2 'Simulation' step (canonical flow Step 4). Use whenever a design needs functional verification: derive the interface (L1/L9), clock/reset (L8/L9), a reference model, a scoreboard, functional coverage, and assertions, then run cocotb. Program-first: the deterministic generator `professional_tb_gen.py` (MCP `eda_professional_tb`) does the derivation; this skill is the judgment layer for filling a non-closed-form reference model and reviewing coverage. Triggers on: 'write a testbench', 'generate testbench', 'verify this design', 'functional verification', 'coverage', '幫我寫 testbench', '產生 testbench', after Phase-2 RTL is authored and before Phase-3.
- ▌ Design For Eco · vibeic bundleDesign-for-ECO methodology — pre-place a distributed pool of tied-off spare standard cells/gates and reserve spare ECO pads so that a late-stage bug can be fixed with a cheap metal-only ECO instead of a full base-layer respin. Covers WHY (metal-only vs base-layer respin cost), WHAT to insert (inverter/nand2/nor2/dff/mux2/aoi/oai mix, ~1-5% density, tie-offs, even spatial distribution, reserved ECO pads), WHERE in the flow (after placement, before CTS), ECO-aware metal fill, and the HARD preservation rule that every downstream optimization must obey. Use when: 'design for eco', 'spare cells', 'ECO prep', 'metal-only ECO readiness', 'reserve spare gates', 'spare pad planning', or before CTS on any digital place-and-route flow.
- ▌ Fpga Signaltap · vibeic bundleAuto-generate Quartus SignalTap II logic analyzer configurations for FPGA debugging. When to use: FPGA BIST fails and UART log isn't enough to diagnose the root cause. Generates .stp file that captures all DUT I/O signals, internal FSM state, and BIST engine state with configurable triggers. Triggers when: 'signaltap', 'debug FPGA', 'capture signals', 'logic analyzer', 'BIST failed need debug', or when Phase 3 FPGA verification fails and more visibility is needed.
- ▌ Eco Plan · vibeic bundlePlan an Engineering Change Order (ECO) — a late-stage design change that minimizes disruption to an already-placed-and-routed netlist. Use when the user says "need an ECO", "late-stage fix", "spin without re-place-and-route", "metal-only fix", or describes a bug found after P&R.
- ▌ Hold Fix · vibeic bundlePost-CTS and post-route hold violation fixing via buffer/delay cell insertion. CTS always introduces hold violations that must be fixed. Use when: 'hold violation', 'hold fix', 'hold slack', 'fix hold', 'negative hold slack', 'post-CTS hold', 'short path padding', or after CTS completes (Step 19).
- ▌ Hls C2rtl · vibeic bundleTranslate C / C++ / SystemC algorithmic descriptions into synthesizable RTL via High-Level Synthesis. Use when the user says "HLS", "C to RTL", "C++ to Verilog", "Vitis HLS", "Catapult", "XLS", "algorithmic design", or provides a reference implementation in software and asks for hardware.
- ▌ Lvs Triage · vibeic bundleTriage Layout-vs-Schematic (LVS) mismatches — missing connections, short/open nets, device parameter mismatches, unmatched instances. Use when the user says "LVS", "layout vs schematic", "LVS mismatch", "netlist compare", "Calibre LVS", "Netgen".
- ▌ Rtl Repair · vibeic bundleAutomatically fix lint violations, synthesis errors, and simulation mismatches in RTL code. Use when the user says "fix this Verilog", "repair the RTL", "resolve these lint errors", "my synthesis is failing", or shares an HDL file with error logs from a lint/synth/sim tool.
- ▌ Rtl Review · vibeic bundleAudit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
- ▌ Sta Review · vibeic bundleRead Static Timing Analysis reports, triage setup/hold/recovery/removal violations, and propose fixes (RTL pipelining, sizing, useful skew, buffer insertion). Use when the user says "STA", "timing report", "timing violation", "setup fail", "hold fail", "close timing", "WNS", "TNS".
- ▌ Ppa Distill · vibeic bundleTurn a PPA recovery that worked into a case with evidence, a design fingerprint that bounds where it may be reused, and a draft of the deterministic rule it should eventually become. Use when the user says "capture this", "we should remember this fix", "distill the lesson", "promote this case", or after any closure loop where judgement recovered a result a program could not.
- ▌ Ppa Measure · vibeic bundleRead PPA artefacts that the tools already wrote — STA reports, power reports, area reports, DEF/GDS summaries — and turn them into an evidence-linked measurement report of canonical `vibeic.ppa.metric.v1` records, each carrying its scope and its native source path. Use when the user says "measure PPA", "what is the real area/power/timing", "collect the PPA numbers", "post-route PPA", or when a report must state what was measured AND what was not.
- ▌ Ppa Predict · vibeic bundleEARLY, PRE-SYNTHESIS ESTIMATE of power, performance and area — a ranged guess produced before any tool has run, never a measurement and never admissible as final PPA. Use when the user says "estimate PPA", "how big will this be", "what's the area of this module", "will this meet timing", or wants a sanity check before committing to a long synthesis run. For numbers parsed out of real tool artefacts, use `ppa-measure` instead — the two must never share a table.
- ▌ Ppa Recover · vibeic bundlePropose a bounded way out when a PPA closure loop has stalled, oscillated, regressed or crashed — naming the rollback point, the blast radius, and the condition under which recovery stops rather than looping. Use when the user says "the loop is stuck", "PnR keeps getting worse", "we regressed", "roll this back", "recover the run", or when a closure controller has exhausted its budget without converging.
- ▌ Spec Review · vibeic bundleReview a natural-language hardware specification for ambiguity, internal inconsistency, untestable statements, and missing corner cases BEFORE it enters spec-to-rtl. Use when the user says "review this spec", "check my spec", "is this spec complete", "spec sanity check", or provides a datasheet draft / PRD for a hardware block.
- ▌ Phase1 · vibeic bundlePhase 1 = the **prompt / dialogue entry point** to the Vibe-IC platform. Takes natural language (Chinese or English), runs the IC Expert Agent dialogue (it faces the user in a plain-language register and owns silicon depth), produces both (a) machine-readable L1-L27 JSON layer docs that feed Phase 2 directly AND (b) human-readable Markdown views of the same content for stakeholder review. Skips Phase 1 entirely — the L1-L27 JSON is the universal handoff format and Phase 1 emits it directly. Triggers when the user says "start a new IC design", "run Phase 1", "design a chip in natural language", provides only a prompt or wants AI to author the spec from scratch.
- ▌ Ams Sim · vibeic bundlePlan and run analog / mixed-signal simulations — DC op, AC, transient, Monte Carlo, corner sweeps, PSRR/CMRR, noise — using ngspice, Xyce, Spectre, or HSPICE, and triage the results. Use when the user says "SPICE", "ngspice", "Monte Carlo", "corner simulation", "analog sim", "AC analysis", "transient", "PSRR", "CMRR", "noise analysis".
- ▌ Drc Fix · vibeic bundleDiagnose and fix Design Rule Check (DRC) violations in a layout or GDS. Use when the user says "fix DRC", "DRC clean", "resolve spacing errors", "my layout fails DRC", or shares a DRC report from Calibre, Klayout, or Magic.