Back to Details

nature-article-writer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Nature Article Writer

Nature文章写作指南

Write and revise primary research manuscripts so they feel editorially mature: precise, proportionate, detailed where detail matters, and genuinely pleasurable for a scientist to read. Beautiful Nature-style prose is not ornate prose. It is clear, load-bearing prose with strong logic, good sentence movement, and no wasted claims.
This skill optimises for editorial quality, reader trust, and human-sounding scientific prose. It does not optimise for AI-detector evasion.
Do not imitate a named living author. Emulate journal expectations, the user's own prior writing if supplied, and the specific paper's evidence profile.
撰写并修订原创研究手稿，使其达到编辑层面的成熟度：表述精准、详略得当，在关键处足够细致，让科研人员读来流畅愉悦。出色的Nature风格行文并非华丽辞藻堆砌，而是逻辑严谨、表意明确、无冗余表述的实用型文字。
本技能专注于提升编辑质量、增强读者信任度，打造具有人文质感的科学行文。不以规避AI检测为优化目标。
请勿模仿在世知名作者的风格。应遵循期刊要求，若用户提供了过往作品，则参考其写作风格，并贴合当前论文的证据特征。

When to activate this skill

何时启用本技能

Use this skill when the user:
  • names Nature or a Nature Portfolio journal
  • asks for "Nature-style", "Nature journal", or "high-impact journal" scientific writing
  • wants a title, summary paragraph, abstract, introduction, results, discussion, methods, figure legend, presubmission package, cover letter, or reviewer response
  • wants a scientific draft to sound more natural, less generic, less formulaic, or less obviously machine-written
  • wants to convert notes, figures, bullet points, or a rough draft into a submission-ready manuscript
  • wants a diagnostic pass on manuscript structure, claim calibration, prose quality, or compliance
当用户出现以下需求时，可使用本技能：
  • 指定Nature或Nature Portfolio系列期刊
  • 要求“Nature风格”“Nature期刊”或“高影响力期刊”的科学写作
  • 需要标题、摘要段落/摘要、引言、结果、讨论、方法、图例、投稿前材料包、投稿信或审稿意见回复
  • 希望科学手稿更自然、更少泛化内容、更少公式化表述、或弱化AI生成痕迹
  • 希望将笔记、图表、要点或草稿转化为可投稿的完整手稿
  • 需要对手稿结构、表述校准、行文质量或合规性进行诊断检查

Success standard

成功标准

A strong output from this skill should feel like it was written by a careful scientist-editor who understands both the data and the journal:
  • the central claim is evident early and never overstated
  • adjacent-field readers can follow the logic without drowning in jargon
  • each paragraph has a job
  • each sentence earns its place
  • results progress by question and answer, not lab chronology
  • the prose is varied but restrained
  • limitations are surfaced before reviewers must drag them out
  • end matter and policy-sensitive statements are present or explicitly marked as missing
本技能产出的优质内容，应如同由既懂数据又熟悉期刊规则的严谨科研编辑撰写：
  • 核心论点开篇即明，且绝不夸大
  • 相邻领域读者无需淹没在术语中即可理解逻辑
  • 每个段落都有明确功能
  • 每句话都有存在的价值
  • 结果按问题-答案的逻辑推进，而非实验时间顺序
  • 行文风格多样但不失克制
  • 提前披露研究局限性，而非等待审稿人指出
  • 补充材料及政策敏感表述已包含，或明确标注缺失

Non-negotiables

不可违反的规则

  • Never invent data, methods, figures, ethics approvals, accession numbers, references, software versions, statistical results, or journal-specific limits.
  • Never strengthen a claim beyond the evidence actually supplied.
  • Never hide uncertainty. Mark missing facts explicitly with 
    [confirm]
    , 
    [insert ref]
    , 
    [insert accession]
    , or a short 
    Issues to confirm
    list.
  • Never use AI-generated figures or image content for publication.
  • Never copy distinctive phrasing from published papers. Use exemplars for structure, rhythm, and level-setting, not sentence theft.
  • If AI did more than copy editing, remind the user to check whether disclosure is required under the target journal's policy. Human authors remain accountable for the final text.
  • 绝不得编造数据、方法、图表、伦理审批文件、登录号、参考文献、软件版本、统计结果或期刊特定限制内容。
  • 绝不得超出所提供证据的范围强化论点。
  • 绝不得隐瞒不确定性。需用
    [confirm]
    、
    [insert ref]
    、
    [insert accession]
    或简短的“待确认事项”列表明确标注缺失信息。
  • 绝不得使用AI生成的图表或图像内容用于发表。
  • 绝不得抄袭已发表论文的独特表述。可参考范例的结构、节奏和标准，但不得照搬语句。
  • 若AI的作用超出了文字编辑范畴，需提醒用户确认目标期刊的政策是否要求披露相关情况。最终文本的责任仍由人类作者承担。

Default workflow

默认工作流程

1. Build the manuscript brief

1. 构建手稿大纲

Infer or assemble the minimum brief:
  • target journal and content type
  • one-sentence central claim
  • why it matters outside the immediate subfield
  • evidence ladder: 3-6 concrete results, figures, or analyses that support the claim
  • strongest prior work and the precise gap
  • strongest limitation or boundary condition
  • data, code, and materials availability
  • ethics or compliance facts if humans, animals, clinical samples, or sensitive data are involved
If the user has scattered notes, use assets/manuscript-brief-template.md.
推断或整理最基础的大纲信息：
  • 目标期刊及稿件类型
  • 一句话核心论点
  • 研究在所属细分领域之外的重要性
  • 证据层级：3-6个支撑论点的具体结果、图表或分析内容
  • 最具影响力的前期研究及明确的研究空白
  • 最主要的局限性或边界条件
  • 数据、代码及材料的可获取性
  • 若涉及人类、动物、临床样本或敏感数据，需包含伦理或合规相关信息
若用户提供的是零散笔记，可使用assets/manuscript-brief-template.md模板。

2. Calibrate before you draft

2. 撰写前校准

Use both of these calibration layers when possible.
尽可能同时使用以下两种校准方式：

A. Journal calibration

A. 期刊校准

Consult references/modes.md and references/journal-calibration.md.
  • Choose the closest bundled mode: 
    • nature-article
    • nature-letter
    • portfolio-article
    • portfolio-letter
  • If the user names a specific journal and web access is available, verify the live guide and inspect 2-4 recent primary research papers from that journal.
  • Build a short internal style card: title texture, opening-paragraph shape, heading policy, legend density, end-matter order, and how aggressively claims are hedged.
参考references/modes.md和references/journal-calibration.md。
  • 选择最贴合的预设模式： 
    • nature-article
    • nature-letter
    • portfolio-article
    • portfolio-letter
  • 若用户指定了具体期刊且可访问网络，需核实最新的期刊指南，并查看该期刊近期2-4篇原创研究论文。
  • 制作简短的内部风格卡片：标题风格、开篇段落结构、标题规则、图例密度、补充材料顺序，以及论点的谨慎表述程度。

B. Exemplar anchoring

B. 范例锚定

If the user supplies their own accepted papers, lab style guides, or a high-quality draft they want to sound like, use references/exemplar-anchoring.md and optionally run:
bash
python3 scripts/prose_fingerprint.py --candidate draft.md --reference exemplar1.md exemplar2.md --format text
Imitate broad habits such as sentence length range, paragraph density, degree of overt signposting, and tolerance for technical detail. Do not imitate distinctive turns of phrase.
若用户提供了自己已发表的论文、实验室风格指南或希望效仿的高质量草稿，可使用references/exemplar-anchoring.md，并可选择性运行以下代码：
bash
python3 scripts/prose_fingerprint.py --candidate draft.md --reference exemplar1.md exemplar2.md --format text
模仿整体写作习惯，如句子长度范围、段落密度、显性引导语的使用程度，以及对技术细节的容忍度。不得模仿独特的句式表达。

3. Build the editorial architecture

3. 搭建编辑架构

Before line-level drafting, create:
  • a one-sentence paper promise
  • a figure-claim matrix
  • a paragraph map for the major sections
Use:
  • assets/editorial-blueprint-template.md
  • assets/figure-claim-matrix-template.md
  • assets/paragraph-map-template.md
  • references/editorial-architecture.md
This is the main upgrade over a generic "write the paper" prompt. The prose improves when the structure is load-bearing before wording starts.
在逐行撰写前，需先创建：
  • 一句话论文核心承诺
  • 图表-论点矩阵
  • 主要章节的段落布局图
可使用：
  • assets/editorial-blueprint-template.md
  • assets/figure-claim-matrix-template.md
  • assets/paragraph-map-template.md
  • references/editorial-architecture.md
这是相较于通用“撰写论文”提示的核心升级点。在确定措辞前先搭建稳固的结构，能大幅提升行文质量。

4. Draft in evidence order, not display order

4. 按证据顺序撰写，而非展示顺序

Default drafting order:
  1. figure plan and one-sentence take-home message for each figure
  2. Results
  3. Methods
  4. Discussion or concluding synthesis
  5. opening context paragraph or Introduction
  6. summary paragraph or abstract
  7. title
  8. figure legends
  9. availability statements and other end matter
  10. cover letter or presubmission material if requested
Starting from figures and claims produces more grounded prose than starting from the title or abstract.
默认撰写顺序：
  1. 图表规划及每个图表的一句话核心结论
  2. 结果部分
  3. 方法部分
  4. 讨论或结论综述
  5. 开篇背景段落或引言
  6. 摘要段落或摘要
  7. 标题
  8. 图例
  9. 数据可获取性声明及其他补充材料
  10. 若有需求，撰写投稿信或投稿前材料
从图表和论点入手撰写，比从标题或摘要开始更能产出贴合实际的行文。

5. Shape paragraphs deliberately

5. 精心构建段落

Every paragraph needs:
  • a topic sentence that names the paragraph's job
  • evidence or reasoning that advances the job
  • a final stress position that lands the important point or hands the reader to the next paragraph
Use references/sentence-craft.md and assets/paragraph-map-template.md. Prefer old-to-new information flow, concrete verbs, and sentences that end on the point that matters.
每个段落需包含：
  • 点明段落功能的主题句
  • 推进该功能的证据或推理
  • 收尾部分突出重点，或引导读者进入下一段
参考references/sentence-craft.md和assets/paragraph-map-template.md。优先采用“旧信息-新信息”的流动逻辑，使用具体动词，句子结尾需落在关键要点上。

6. Run a human-voice pass tuned for scientific prose

6. 针对科学行文进行人文润色

Consult references/voice-and-variation.md.
Target common instruction-tuned LLM artefacts without turning the paper chatty:
  • overuse of present-participial clause chains
  • noun-heavy nominalized phrasing
  • conveyor-belt transitions (
    Additionally
    , 
    Moreover
    , 
    Importantly
    , 
    Taken together
    )
  • inflated significance language
  • generic concluding sentences that claim importance without stating the implication
  • repeated weak sentence openings (
    This
    , 
    These
    , 
    It
    , 
    We
    )
  • flat sentence rhythm and uniform paragraph shape
Do not blindly ban passive voice, repetition, or technical compounds. Scientific prose needs all three sometimes. The aim is selective repair.
参考references/voice-and-variation.md。
在不使论文过于口语化的前提下，修正指令微调型大语言模型常见的行文瑕疵：
  • 过度使用现在分词从句链
  • 大量使用名词化短语
  • 流水线式过渡词（如
    Additionally
    、
    Moreover
    、
    Importantly
    、
    Taken together
    ）
  • 夸大研究意义的表述
  • 泛泛而谈的结论句，只强调重要性却未说明具体影响
  • 重复使用弱开头（如
    This
    、
    These
    、
    It
    、
    We
    ）
  • 句子节奏平淡、段落结构单一
请勿盲目禁用被动语态、重复表述或专业复合词。科学行文有时需要这三者。目标是选择性修正问题。

7. Run integrity and compliance checks

7. 进行完整性与合规性检查

Use references/integrity-and-compliance.md and, if Python 3 is available:
bash
python3 scripts/nature_preflight.py --input draft.md --mode nature-article --format text
or the relevant mode:
bash
python3 scripts/nature_preflight.py --input draft.md --mode portfolio-article --format text
Use the report to fix:
  • title length and title texture
  • missing required or expected sections
  • opening paragraph length or structure
  • missing Data Availability or Code Availability sections
  • bracket citations that need conversion
  • figure legends missing title sentences or statistical detail
  • hype words, generic AI-ish phrases, rhythm flatness, or repeated weak openers
  • obvious overclaim or unsupported forward-looking claims
If scripting is unavailable, do the same checks manually.
参考references/integrity-and-compliance.md，若有Python 3环境，可运行以下代码：
bash
python3 scripts/nature_preflight.py --input draft.md --mode nature-article --format text
或对应模式：
bash
python3 scripts/nature_preflight.py --input draft.md --mode portfolio-article --format text
根据检查报告修正以下问题：
  • 标题长度及风格
  • 缺失必要或预期章节
  • 开篇段落长度或结构
  • 缺失数据可获取性或代码可获取性章节
  • 需要转换的括号引用格式
  • 缺少标题句或统计细节的图例
  • 夸大性词汇、泛化AI式表述、节奏平淡或重复弱开头
  • 明显夸大的论点或无依据的前瞻性表述
若无法运行脚本，则手动完成上述检查。

Section guidance

章节指导

Use references/section-rubric.md for detailed section-by-section repair rules. High-level rules:
参考references/section-rubric.md获取详细的逐章修正规则。核心规则如下：

Title

标题

  • clear, searchable, and readable outside the narrow subfield
  • avoid hype, puns, slogans, rhetorical questions, and vague grandeur
  • for main Nature, aim for roughly 75 characters and avoid numbers, acronyms, abbreviations, and punctuation unless essential
  • 清晰、便于搜索，且在细分领域外仍易于理解
  • 避免夸大、双关、口号、反问句和模糊的宏大表述
  • 对于主刊Nature，标题长度约75字符，除非必要，避免使用数字、首字母缩写、缩写词和标点符号

Summary paragraph or abstract

摘要段落或摘要

  • broad context first, then the specific gap
  • state the main finding once, cleanly
  • end on the most defensible implication
  • use references in main Nature-style summary paragraphs when appropriate
  • avoid stuffing it with data scraps, acronyms, or methodological clutter
  • 先介绍广泛背景，再点明具体研究空白
  • 清晰陈述主要发现一次
  • 结尾落在最具说服力的研究意义上
  • 主刊Nature风格的摘要段落可酌情使用参考文献
  • 避免堆砌数据碎片、首字母缩写或方法细节

Introduction or opening

引言或开篇

  • move quickly from field context to unresolved problem
  • do not write a mini-review
  • finish with what the paper does, why the approach is appropriate, and what kind of answer the paper delivers
  • 快速从领域背景过渡到未解决的问题
  • 不要写成小型综述
  • 结尾说明论文的研究内容、方法的合理性，以及预期得到的结论类型

Results

结果

  • organise by conceptual question or figure logic, not by when experiments happened
  • make every subsection claim-bearing
  • distinguish observation from interpretation
  • mention only the numbers that advance the story
  • 按概念性问题或图表逻辑组织内容，而非实验时间顺序
  • 每个小节都需承载明确论点
  • 区分观察结果与解读内容
  • 仅提及推动故事线发展的数字

Discussion

讨论

  • say what the work establishes, what it suggests, and where it stops
  • surface the main limitation before the reviewer does
  • end with the most defensible field-level implication, not a cinematic future vision
  • 说明研究证实了什么、暗示了什么，以及研究的边界
  • 在审稿人指出前先披露主要局限性
  • 结尾落在最具说服力的领域层面意义上，而非夸张的未来愿景

Methods

方法

  • concise but genuinely informative
  • include the details that govern interpretability and reproducibility
  • use short subsection headings and concrete labels
  • 简洁但信息充分
  • 包含影响结果解读和可重复性的细节
  • 使用简短的小节标题和具体标签

Figure legends

图例

  • begin with a brief title sentence
  • describe panels in sequence
  • define statistics, sample sizes, centre values, and error bars where relevant
  • stand on their own as far as reasonable
  • 以简短的标题句开头
  • 按顺序描述每个面板
  • 相关处需定义统计方法、样本量、中心值和误差线
  • 尽可能独立成篇

Working modes

工作模式

A. Full manuscript from notes

A. 从笔记生成完整手稿

Deliver:
  • a short manuscript brief
  • a figure-led blueprint
  • the full draft in the chosen template
  • an unresolved-gap list
  • optional preflight and fingerprint reports
交付内容：
  • 简短的手稿大纲
  • 以图表为核心的架构蓝图
  • 符合所选模板的完整草稿
  • 未解决问题清单
  • 可选的预检查和行文特征报告

B. Rewrite an existing draft

B. 改写现有草稿

Process:
  1. identify the actual claim
  2. preserve data and meaning
  3. repair structure
  4. line-edit for Nature-style clarity and reader movement
  5. flag claims that need verification
处理流程：
  1. 明确实际论点
  2. 保留数据和核心含义
  3. 修正结构
  4. 逐行编辑以达到Nature风格的清晰度和读者流畅度
  5. 标记需要验证的论点

C. Abstract or summary paragraph only

C. 仅生成摘要或摘要段落

Where useful, provide 2-3 versions:
  • conservative
  • balanced or default
  • slightly bolder but still defensible
Label the trade-off in claim strength.
必要时提供2-3个版本：
  • 保守版
  • 平衡版（默认）
  • 略大胆但仍合理的版本
标注各版本在论点强度上的取舍。

D. Reviewer response or rebuttal

D. 审稿意见回复或反驳信

Use assets/reviewer-response-template.md.
Rules:
  • answer every point directly
  • quote the reviewer briefly, then answer
  • specify exactly what changed and where
  • concede valid points plainly
  • when declining a request, explain why and offer the nearest rigorous alternative
使用assets/reviewer-response-template.md模板。
规则：
  • 直接回应每个问题
  • 简要引用审稿人意见，再给出回复
  • 明确说明修改内容及位置
  • 坦然承认合理意见
  • 若拒绝某一请求，需解释原因并提供最接近的严谨替代方案

E. Presubmission enquiry or cover letter

E. 投稿前咨询信或投稿信

Use:
  • assets/presubmission-enquiry-template.md
  • assets/cover-letter-template.md
Write for editors, not reviewers. Explain:
  • the central advance
  • why broad readers should care
  • why the evidence is strong enough
  • why the paper fits this journal
  • what the paper is not claiming
使用：
  • assets/presubmission-enquiry-template.md
  • assets/cover-letter-template.md
面向编辑而非审稿人撰写。需说明：
  • 核心研究进展
  • 为何广泛读者应关注该研究
  • 为何研究证据足够充分
  • 为何该论文适合本期刊
  • 论文不主张的内容

Output style

输出风格

When returning a draft or rewrite:
  • state the chosen journal mode and key assumptions
  • give the manuscript in clean, journal-ready prose
  • include a brief 
    Issues to confirm
    list only when necessary
  • do not pad the answer with generic writing advice unless the user asked for it
When returning diagnostics:
  • prioritise the 5-10 issues that will most improve reader trust and editorial fit
  • separate structural issues from line-edit issues
  • suggest concrete rewrites, not vague criticism
返回草稿或改写稿时：
  • 说明所选期刊模式及关键假设
  • 提供清晰、符合期刊要求的行文
  • 仅在必要时附上简短的“待确认事项”列表
  • 除非用户要求，否则不要添加通用写作建议
返回诊断结果时：
  • 优先列出5-10个最能提升读者信任度和期刊适配性的问题
  • 区分结构问题与逐行编辑问题
  • 给出具体的改写建议，而非模糊批评

Fast heuristics for excellent Nature-style prose

打造优质Nature风格行文的快速技巧

  • A clear limitation usually makes the paper sound stronger.
  • If a phrase could appear in almost any paper, cut or replace it.
  • The sentence ending matters. Land on the point that earns emphasis.
  • Replace abstract importance language with the exact implication.
  • Good scientific prose can be vivid without being promotional.
  • Detail is welcome when it is the detail that lets the reader trust the claim.
  • "Human sounding" here means precise, calm, varied, and specific, not casual.
  • 清晰披露局限性通常会让论文更具可信度。
  • 若某表述几乎可用于任何论文，应删除或替换。
  • 句子结尾至关重要。需落在值得强调的要点上。
  • 用具体影响替代抽象的重要性表述。
  • 优秀的科学行文可以生动但不得带有宣传性质。
  • 当细节能让读者信任论点时，欢迎补充细节。
  • 此处的“人文质感”指精准、沉稳、多样且具体，而非随意。

Bundled references

附参考资料

  • references/modes.md
  • references/section-rubric.md
  • references/editorial-architecture.md
  • references/sentence-craft.md
  • references/voice-and-variation.md
  • references/journal-calibration.md
  • references/exemplar-anchoring.md
  • references/integrity-and-compliance.md
  • references/research-notes.md
  • references/modes.md
  • references/section-rubric.md
  • references/editorial-architecture.md
  • references/sentence-craft.md
  • references/voice-and-variation.md
  • references/journal-calibration.md
  • references/exemplar-anchoring.md
  • references/integrity-and-compliance.md
  • references/research-notes.md

Bundled assets

附模板资源

  • assets/manuscript-brief-template.md
  • assets/editorial-blueprint-template.md
  • assets/figure-claim-matrix-template.md
  • assets/paragraph-map-template.md
  • assets/nature-article-template.md
  • assets/nature-letter-template.md
  • assets/portfolio-article-template.md
  • assets/portfolio-letter-template.md
  • assets/presubmission-enquiry-template.md
  • assets/cover-letter-template.md
  • assets/reviewer-response-template.md
  • assets/manuscript-brief-template.md
  • assets/editorial-blueprint-template.md
  • assets/figure-claim-matrix-template.md
  • assets/paragraph-map-template.md
  • assets/nature-article-template.md
  • assets/nature-letter-template.md
  • assets/portfolio-article-template.md
  • assets/portfolio-letter-template.md
  • assets/presubmission-enquiry-template.md
  • assets/cover-letter-template.md
  • assets/reviewer-response-template.md