isca-writing-style
Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.
# ISCA Writing Style An ISCA paper is an argument that a piece of machine organization should exist. The prose conventions below are how the architecture community expects that argument to be laid out — learned from the venue's canon and enforced, softly but consistently, by its reviewers. Format facts (11 pages of single-spaced two-column text excluding references, IEEE-flavored template for the 2026 edition) are the verified 2026 snapshot; recheck the current guidelines page before formatting. ## One insight, stated as a mechanism-behavior link Before drafting, complete this sentence and pin it above the desk: > Because <structural property of workloads or designs>, organizing the hardware as > <mechanism> yields <behavioral consequence>, which we demonstrate by <instrument>. Every section either supports that sentence or gets cut. Papers with two ideas do worse than either idea alone at this venue — the review form's "key contribution" box forces a choice, and reviewers make it less charitably than authors would. ## The load-bearing motivation section The distinctive ISCA move is Section 2 as a *measured* motivation: characterization data showing the problem exists at magnitude,
- One insight, stated as a mechanism-behavior link
- The load-bearing motivation section
- Mechanism description at checkable precision
- Calibrated numbers, always with their instrument
- Budgeting the 11 pages
- Sentence-level habits of accepted papers
- Revision-friendliness is a 2026-cycle feature
- Self-edit gate before the deadline
What does the isca-writing-style skill do?
Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.