dac-related-work
Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DAC Related Work Position the paper against the EDA literature a DAC reviewer already knows. At six double-column pages, related work is not a survey — it is a **delta statement**: here is the best prior technique for this design task, here is precisely what it cannot do, here is what we add, measured in QoR. DAC reviewers are drawn from exactly the subcommittee whose prior work you are extending, so an incomplete or unfair positioning is caught immediately. ## The EDA literature lanes Cover the lanes your contribution touches; do not pad with distant ones: - **The top EDA venues** — DAC, **ICCAD**, **DATE**, **ASP-DAC** — the conference record of your problem. A physical-design paper that cites no recent DAC/ICCAD placement work reads as disconnected. - **The EDA journals** — **IEEE TCAD** (Transactions on CAD) and **ACM TODAES** — where the extended and most authoritative versions of techniques live; cite the journal version when it is the canonical reference. - **Adjacent communities when relevant** — ISCA/MICRO/HPCA for architecture-facing work, ITC/VTS for test, ISSCC/CICC for circuits, and the ML venues (NeurIPS/ICML/ICLR) *only* when your ML-for-EDA method genuinely builds
- The EDA literature lanes
- Delta-first positioning
- Name the strongest baseline as the thing to beat
- Honest benchmark and reproducibility lineage
- Third-person self-citation under double-blind
- Fitting related work into six pages
- Output format
What does the dac-related-work skill do?
Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-related-work --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.