← ClaudeAtlas

paper-writing-stylelisted

House style rules for scientific paper writing in English, distilled from Valtencir Zucolotto's scientific writing course. Load whenever drafting, revising, or reviewing any part of a scientific manuscript (abstract, introduction, results, discussion, conclusions, cover letter) so the prose reads as clear, concise, specific, human-written academic English rather than generated text. Also load when asked to humanize, tighten, or de-jargon scientific prose.
yuryalencar/ai-skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill yuryalencar/ai-skills
# Scientific writing house style Rules for producing English scientific prose that an editor of a high impact journal would accept. Apply them when writing or reviewing any manuscript section. Two words govern everything: **clarity** and **concision**. Clarity is the message reaching the reader's mind as fast as possible. Concision is doing that with the fewest words. Every sentence must carry one idea to the reader. ## Project layout and conventions Four things to establish before writing a single line, all covered in `references/latex-conventions.md`: 1. **The project's own `CLAUDE.md` outranks these defaults.** A working paper repository documents its layout, section files, label convention, page limit and data provenance rules. Read it first and follow it. Never restructure a project to match a default. 2. **Sections live one per file in `src/`**, with `main.tex` holding the preamble, title block and `\input` order. **Read the `\input` list to learn what the project calls things** rather than assuming: `conclusion.tex` and `conclusions.tex` both occur, results and discussion may be one file or two, and methods may be `study-design.tex`. 3. **Read `src/macros.tex`.** Recurring values and terminology are defined there so they stay consistent. Write `\nparticipants participants`, not `54 participants`. Write `\RQ{1}`, not `\textbf{RQ1}`. When a value changes, change the macro, not the prose. When a value recurs and has no macro, propose one. If `