hpca-topic-selection
Use when deciding whether a project is HPCA-shaped or better routed to ISCA, MICRO, ASPLOS, or a systems/theory venue, weighing whether the machine, the mechanism, or the measurement is the contribution, and whether the main track or the HPCA Industry track fits, from the winter seat of the architecture calendar.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-topic-selection --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.
# HPCA Topic Selection Use this before committing a project to HPCA. The question is not "is this architecture?" but "is the contribution a **measured microarchitectural cost met by a buildable mechanism** whose behavior is shown on a credible instrument?" If yes, HPCA fits; if the center of gravity is elsewhere, route deliberately. ## The three centers of gravity Locate where the novelty actually
What does the hpca-topic-selection skill do?
Use when deciding whether a project is HPCA-shaped or better routed to ISCA, MICRO, ASPLOS, or a systems/theory venue, weighing whether the machine, the mechanism, or the measurement is the contribution, and whether the main track or the HPCA Industry track fits, from the winter seat of the architecture calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-topic-selection --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.