jais-writing-style
Use when polishing the prose of a Journal of the Association for Information Systems (JAIS) manuscript — the abstract, introduction, theory narrative, and APA-6 mechanics — so a pluralistic, theory-forward reviewer pool can follow the argument. A late-stage polish; it does not build the contribution (jais-contribution-framing) or check submission mechanics (jais-submission).
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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.
# Writing Style (jais-writing-style) ## When to trigger - The theory, evidence, and contribution are settled and the prose now needs to carry them - The introduction reads as a literature dump and the contribution does not land in the first pages - Your sub-field's shorthand makes the paper opaque to reviewers from other IS traditions - References and in-text citations are not in APA 6th edition - A reviewer says the writing is "dense," "jargon-heavy," or "the argument is hard to follow" ## Write for a pluralistic, theory-forward reader JAIS reviewers span behavioral, economic, design-science, organizational, and critical/philosophical traditions, and the journal prizes "innovative, interesting and rigorously developed" work. Your prose must therefore do two things at once: make the **theoretical argument** vivid and primary, and stay legible to a reader who does not share your methodological dialect. Define terms the first time; explain why a move matters before you make it; lead with ideas, not apparatus. ## The introduction is the contribution, told as a story A JAIS introduction should, in roughly its first two pages, answer: what is the IS phenomenon, why is it interesting and
- When to trigger
- Write for a pluralistic, theory-forward reader
- The introduction is the contribution, told as a story
- Define constructs before you use them
- Foreground the theory, then the evidence
- Write the abstract to do its job across traditions
- Prose mechanics JAIS reviewers notice
- Match the prose register to the category
- Respect double-blind anonymity in the prose
- Mind the length while polishing
- Checklist
- Worked vignette: rewriting an opening for JAIS (illustrative)
- Anti-patterns
- Output format
What does the jais-writing-style skill do?
Use when polishing the prose of a Journal of the Association for Information Systems (JAIS) manuscript — the abstract, introduction, theory narrative, and APA-6 mechanics — so a pluralistic, theory-forward reviewer pool can follow the argument. A late-stage polish; it does not build the contribution (jais-contribution-framing) or check submission mechanics (jais-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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.