Menú
Evaluate whether the current BSPDN PDN contract is strong enough under `BPR reserved for PDN`, separating PDN sufficiency from signal-mixing questions.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Creates and refines academic presentations from research papers. Use this skill for tasks involving the conversion of scientific or technical documents into slide decks for conferences, seminars, lectures, thesis defenses, or academic reviews. Supports beamer LaTeX (.tex), PowerPoint (.pptx), and Markdown output formats.
Execute delay-model validation gates against HPWL baselines. Use when evaluating model consistency, running Gate-0 contract checks, building Gate-1 bucketed scorecards, performing wirelength-aware correlation checks, or deciding readiness for active optimization.
Run a full EDA research chain from knowledge exploration and paper triage to idea debate, hypothesis experiment design, implementation, git versioning, validation, and retrospective. Use when the user requests an end-to-end EDA research workflow rather than a single isolated execution step.
Audit and refine academic manuscripts for structure, terminology consistency, LaTeX hygiene, and high-signal grammar fixes. Use this skill for theses, papers, proposals, and technical reports when the task is manuscript writing rather than experiment execution.
Diagnose and implement backside-routing realization paths, including targeted reroute, local DEF/OpenDB patching, and OpenROAD-backed net-level rerouter bring-up, when theory predicts benefit but the current flow does not realize BM2/BM1 usage.
Audit whether the local BSPDN physical contract is coherent across paper assumptions, GT3 tech collateral, layer/via topology, and current flow policy before promotion or expensive attribution experiments.
| name | bspdn-pdn-sufficiency-evaluator |
| description | Evaluate whether the current BSPDN PDN contract is strong enough under `BPR reserved for PDN`, separating PDN sufficiency from signal-mixing questions. |
Use this skill when the question is "is the current PDN contract strong enough?" rather than "did backside signal routing help?"
Use this skill when:
BPR + current backside PDN is sufficient,Strict-BPR, PDN-boost, or Stress-check comparisons need a dedicated evaluator,BPR.This skill owns:
PDN under-strength vs topology invalidity vs case unsuitability.It does not own:
bspdn-physical-contract-auditor,front-only / CTS-backside-only / partial-signal-backside,Use this family by default:
Strict-BPRPDN-boostStress-check*.results.tsv*.conclusion.md*.experience_delta.mdBPR; that changes the question.BPR-reserved-for-PDN intact unless the physical contract is separately overturned.PDN-boost result implies "strengthen PDN", not "relax the signal contract".references/background-knowledge-links.md for the current summarized PDN-sufficiency knowledge contract.references/update-mechanism.md when deciding whether the evaluator's assumptions or pass/fail criteria need refresh.