uist-writing-style
Use when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth, pairing every capability claim with a figure or measurement, and fitting the argument inside the 10-page or 5-page two-column limit.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.
# UIST Writing Style A UIST paper is a guided tour of a working thing. The reader should experience the system before dissecting it, believe the engineering because it is specified, and finish knowing exactly which piece they could reuse. This is a different rhetoric from an empirical HCI paper (argument from study design) and from an ML paper (argument from benchmark deltas). Format facts below are the 2026 cycle's (two-column `acmart`, 10-page standard / 5-page short, references and appendices excluded); verify against the current Author Guide. ## The UIST arc | Section | Job | Failure smell | |---|---|---| | Abstract + teaser figure | Name the artifact, the enabling idea, one number | No artifact named; "we explore..." | | Introduction | What becomes possible that wasn't; contribution list | Motivation essay with the system in ¶5 | | Walkthrough / scenario | Reader operates the system vicariously, figure-driven | Mechanism dumped before experience | | Design rationale | The 2-4 decisions that define the system, with rejected alternatives | A feature inventory | | Implementation | Enough specificity to re-implement: architecture, algorithms, parts, timings | "Built in Unity" as t
- The UIST arc
- Implementation prose that earns trust
- Claim discipline
- Fitting the page budget
- Figures do half the arguing
- Language habits of accepted systems papers
- Revision passes
- Output format
What does the uist-writing-style skill do?
Use when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth, pairing every capability claim with a figure or measurement, and fitting the argument inside the 10-page or 5-page two-column limit.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-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.