dac-writing-style
Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style --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 Writing Style Use this while writing the body. DAC Research Manuscripts live inside a **6-page double-column budget** (plus a references-only page), so the writing discipline is not "explain everything" but "prove one design-automation contribution, in the field's own QoR currency, in six dense pages." DAC reviewers are EDA experts under time pressure; they decide fast whether the paper has a real, measured advance. ## The DAC first-page arc Front-load the contribution. By the end of the first column-and-a-half a reviewer should know: 1. **The design problem** — a concrete EDA/chip-design task (placement, timing closure, functional verification, IR-drop prediction, IP protection) that the community recognizes. 2. **Why the current state is inadequate** — the specific limitation of the best existing tool or technique, ideally with a number (it does not scale past N cells, it leaves X% negative slack). 3. **The contribution as a measured delta** — the new mechanism *and* the headline QoR result: "we reduce total negative slack by X% at equal area with Y× lower runtime versus [state of the art] on [standard benchmark]." 4. **Why it generalizes** — that the mechanism is not a one
- The DAC first-page arc
- State the contribution as a QoR claim
- Living in six double-column pages
- EDA figures that survive double-column at 9-10 pt
- Third-person self-citation (double-blind)
- Common DAC prose failures
- Output format
What does the dac-writing-style skill do?
Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-writing-style --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.