ppa-optimize

Propose bounded, reversible actuator moves that trade power, performance, and area in IC design closure loops.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing timing, power, and area targets in IC design often devolves into guesswork: a change is applied and the same agent that proposed it declares success. This Skill produces structured, falsifiable PPA optimization proposals where every candidate carries an actuator, a predicted effect, a named remeasurement, and a rollback, so no improvement is ever claimed without independent measurement. ## Core Features & Use Cases - Falsifiable candidate proposals: Each move names the actuator (e.g., placement density 0.62 to 0.58), the predicted effect in metric-record units, the remeasurement scope, and the exact rollback state. - Pareto frontier ranking: Candidates are ranked on the power-performance-area frontier without collapsing to a single weighted score, so it stays visible which axis paid. - Deterministic verdict boundary: The proposal never issues a pass/fail; verdicts belong to deterministic programs (_ppa/feasibility.py, _ppa/pareto.py) after ppa-measure re-reads the artefacts. - Use Case: A designer misses setup timing by 0.124 ns at post_route_extracted. The Skill emits candidates such as loosening placement density or raising synthesis effort, each with predicted WNS delta, remeasurement plan, rollback, and iteration budget, ready for a closure controller to actuate. ## Quick Start Ask the assistant to propose PPA optimization candidates for the current design given the baseline ppa-measure records, the missed timing target, and a budget of six PnR iterations.

Frequently Asked Questions about ppa-optimize

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

FAQPage Schema
How do I propose PPA improvements for an IC design missing timing closure?▼

Provide the baseline canonical metric records from ppa-measure, the missed target and scope, the legal actuators, and the iteration budget. The Skill returns ranked candidates, each with an actuator move, predicted effect, remeasurement plan, and rollback.

What actuators can a PPA optimization proposal adjust?▼

Typical actuators include placement density, clock period, synthesis effort scoped to a module, buffering, and floorplan aspect ratio. Each must be reversible, visible in a config diff, and legal for the design's constraints.

Does the ppa-optimize skill report whether a change worked?▼

No. It only emits predictions and the remeasurement that would falsify them. Pass/fail verdicts come from deterministic programs like _ppa/feasibility.py after ppa-measure re-reads the artefacts at the same scope.

Why must every PPA candidate include a rollback plan?▼

A move without a rollback is a commitment, not a candidate. The rollback states the exact design state to restore, and placeholder values like n/a are rejected by the compliance checker because they hide irreversibility.

Can PPA proposals compare results across different stages or corners?▼

No. Comparing a candidate against a baseline at a different stage, corner, mode, or activity basis is reported as UNDETERMINED. The baseline scope is pinned first and every remeasurement must name the same scope.