From academic-writing
Proofread paper for style, clarity, and grammar. Use when polishing a draft for language quality, fixing typos, improving sentence structure, ensuring consistent terminology, or preparing a manuscript for submission. Trigger whenever the user asks to proofread, polish, copy-edit, check grammar, improve writing quality, or do a final pass on any academic paper, LaTeX document, or manuscript section — even if they just say "can you clean this up" or "check my writing."
npx claudepluginhub jasonbian97/jason-cc-skills --plugin academic-writingThis skill uses the workspace's default tool permissions.
Polish a draft for language quality, applying proven scientific writing principles to improve readability and professionalism.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Polish a draft for language quality, applying proven scientific writing principles to improve readability and professionalism.
Before proofreading, read references/writing-guide.md for detailed style rules and examples.
Effective proofreading requires multiple focused passes. Trying to catch everything at once causes you to miss things. Work through these passes in order:
Read the paper end-to-end without editing. Focus on:
Flag structural issues but don't fix them yet — fixing structure changes text, making later passes on the original version wasted effort.
Apply the 7 reader-expectation principles from references/writing-guide.md (§ Sentence-Level Clarity):
Also check:
Work through the checklist below item by item. Pay special attention to:
Check compilation output and LaTeX conventions (see checklist below).
$x$ everywhere, not sometimes italic text)\%, \_, \&)Figure~\ref{fig:x}, Table~\ref{tab:y}, Section~\ref{sec:z}\cite{}, \ref{}, \eqref{}\emph{} vs \textit{} vs \textbf{}\citet{} for narrative citations, \citep{} for parenthetical (if the template supports natbib; otherwise stay consistent with existing convention)\label{} prefixes: fig:, tab:, sec:, eq:\usepackage{microtype} in preamble for improved typography\cite{} keys resolve (no undefined references).bib, or in .bib but never cited)\ref{} matches \label{})When the draft exceeds the page limit:
| Technique | How | Impact |
|---|---|---|
\looseness=-1 | Place before a paragraph's blank line | Squeezes paragraph by ~1 line |
| Move content to appendix | Move proofs, extra ablations, implementation details | Can save 0.5-2 pages |
| Condense related work | Convert to shorter paragraph form | Saves 0.25-0.5 pages |
| Tighten figure placement | Use [t] or [h] float specifiers; adjust \textfloatsep | Reduces whitespace |
| Reduce figure size | \includegraphics[width=0.45\linewidth] | Fits more per page |
| Combine small tables | Merge related tables side by side | Eliminates float overhead |
Use \paragraph{} | Replace \subsubsection{} with inline headings | Saves vertical space |
Do not modify margins, font sizes, or spacing commands in the style file — this violates venue formatting rules and risks desk rejection.
references/writing-guide.md