dac-camera-ready
Use when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-camera-ready --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 Camera-Ready Use this after an accept decision to produce the archival version. The DAC camera-ready is an **ACM Digital Library** deliverable: ACM is the 2026 copyright holder, and the final manuscript plus copyright form are due at the April proceedings deadline (DAC 2026: ~14 April 2026, after the ~9 March notification). The camera-ready is a controlled edit of the accepted paper, not a rewrite — scope, claims, and QoR numbers are fixed by what was reviewed. ## De-anonymize systematically The review version was double-blind; the camera-ready restores identity. Do it as a checklist so nothing is missed and nothing new leaks in: - **Author block** — full author list, affiliations, and contact, in the order and form you want cited for years. - **Self-citations** — convert third-person references to your own prior work back to first person where natural ("in our earlier work [7]"), now that identity is public. - **Acknowledgements and funding** — restore the acknowledgements and **grant numbers** you stripped for review; funders often require exact wording. - **Tool/repository names** — restore the real tool name and any public artifact/OpenROAD-flow link you anonymized. ## AC
- De-anonymize systematically
- ACM copyright and rights stamp
- The page budget still binds
- ACM DL metadata and archival flow
- Production checklist
- Reverify each cycle
- Output format
What does the dac-camera-ready skill do?
Use when preparing the final ACM/IEEE Design Automation Conference (DAC) Research-Manuscript camera-ready after acceptance, covering de-anonymization, restoring author/affiliation/acknowledgement/funding blocks, the ACM copyright form and rights stamp, the April proceedings deadline, ACM Digital Library metadata and archival-flow checks, and the still-fixed 6+1 page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-camera-ready --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.