asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.
# ASPLOS Writing Style Two 2027 mechanics dictate ASPLOS prose (CFP, checked 2026-07-08): the rapid review reads **only the first two pages**, and the 11-page limit counts **all text, figures, tables, and footnotes** — references excluded. The first makes pages 1-2 a survival organ; the second makes every figure a budget decision. Style here is mostly resource allocation. ## Engineering pages 1-2 as a standalone document By the bottom of page 2, a screener must hold four things. Audit for them mechanically, in order: | Element | Test | Common failure | |---|---|---| | Cross-layer problem | Can a reader from any of the three communities restate it? | A single-community problem with "co-design" sprinkled on | | One-sentence insight | Is there a sentence a screener could quote in their note? | Insight diffused across three paragraphs, or a category ("we co-design X and Y") instead of an idea | | Mechanism sketch | Does the reader know what each layer *does*? | Architecture described, software hand-waved (or vice versa) | | Headline evidence | Result + platform class (silicon/FPGA/simulator) + baseline named? | "Significant improvements on a variety of workloads" | Corollary: backgroun
- Engineering pages 1-2 as a standalone document
- The insight sentence
- Structuring the mechanism across layers
- Claim calibration, systems dialect
- The 11-page budget with figures inside it
- House-rule details that mark a native submission
- A load-order for the abstract
- Section skeleton that serves three readerships
- Revision-aware prose
- Output format
What does the asplos-writing-style skill do?
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.