Skip to content

Yuan1z0825/nature-skills / skills/nature-writing

nature-writing

Verified

Draft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence.

FileKindSize
README.mdmarkdown4.3 KB
README_EN.mdmarkdown4.9 KB
SKILL.mdskill md8.1 KB
agents/openai.yamlconfig253 B
manifest.yamlconfig8.5 KB
references/abstract.mdmarkdown4.0 KB
references/article-architecture.mdmarkdown3.4 KB
references/chinese-author-workflow.mdmarkdown1.8 KB
references/conclusion.mdmarkdown1.2 KB
references/examples/abstract-examples.mdmarkdown875 B
references/examples/abstract/template-a.mdmarkdown950 B
references/examples/abstract/template-b.mdmarkdown3.2 KB
references/examples/abstract/template-c.mdmarkdown1.7 KB
references/examples/index.mdmarkdown2.3 KB
references/examples/introduction-examples.mdmarkdown1.5 KB
references/examples/introduction/novel-task-challenge-decomposition.mdmarkdown1.5 KB
references/examples/introduction/pipeline-not-recommended-abstract-only.mdmarkdown2.9 KB
references/examples/introduction/pipeline-version-1-one-contribution-multi-advantages.mdmarkdown2.0 KB
references/examples/introduction/pipeline-version-2-two-contributions.mdmarkdown2.0 KB
references/examples/introduction/pipeline-version-3-new-module-on-existing-pipeline.mdmarkdown1.5 KB
references/examples/introduction/pipeline-version-4-observation-driven.mdmarkdown1.4 KB
references/examples/introduction/technical-challenge-version-1-existing-task.mdmarkdown2.6 KB
references/examples/introduction/technical-challenge-version-2-existing-task-insight-backed-by-traditional.mdmarkdown3.8 KB
references/examples/introduction/technical-challenge-version-3-novel-task.mdmarkdown1.6 KB
references/examples/introduction/version-1-task-then-application.mdmarkdown727 B
references/examples/introduction/version-2-application-first.mdmarkdown405 B
references/examples/introduction/version-3-general-to-specific-setting.mdmarkdown847 B
references/examples/introduction/version-4-open-with-challenge.mdmarkdown1.7 KB
references/examples/method-examples.mdmarkdown1.0 KB
references/examples/method/example-of-the-three-elements.mdmarkdown7.3 KB
references/examples/method/method-writing-common-issues-note.mdmarkdown355 B
references/examples/method/module-design-instant-ngp.mdmarkdown4.5 KB
references/examples/method/module-motivation-patterns.mdmarkdown410 B
references/examples/method/module-triad-neural-body.mdmarkdown763 B
references/examples/method/neural-body-annotated-figure-text.mdmarkdown2.8 KB
references/examples/method/overview-template.mdmarkdown2.0 KB
references/examples/method/pre-writing-questions.mdmarkdown479 B
references/examples/method/section-skeleton.mdmarkdown110 B
references/experiments.mdmarkdown4.7 KB
references/introduction.mdmarkdown15.3 KB
references/method.mdmarkdown6.9 KB
references/nat-comms-2025-corpus.mdmarkdown7.3 KB
references/nature-summary-paragraph.mdmarkdown10.3 KB
references/paper-review.mdmarkdown5.3 KB
references/paragraph-flow.mdmarkdown1.7 KB
references/related-work.mdmarkdown1.3 KB
references/submission-package.mdmarkdown7.9 KB
static/core/output-format.mdmarkdown1.8 KB
static/core/stance.mdmarkdown2.2 KB
static/core/workflow.mdmarkdown5.1 KB
static/fragments/journal/generic.mdmarkdown1.1 KB
static/fragments/journal/nat-comms.mdmarkdown3.1 KB
static/fragments/journal/nat-mach-intell.mdmarkdown5.9 KB
static/fragments/journal/nature-family.mdmarkdown1.2 KB
static/fragments/journal/nature.mdmarkdown2.7 KB
static/fragments/language/en.mdmarkdown1.0 KB
static/fragments/language/zh-to-en.mdmarkdown1.6 KB
static/fragments/paper_type/algorithmic.mdmarkdown1.2 KB
static/fragments/paper_type/hypothesis.mdmarkdown1.0 KB
static/fragments/paper_type/methods.mdmarkdown1.2 KB
static/fragments/paper_type/research.mdmarkdown1.3 KB
static/fragments/paper_type/review.mdmarkdown1.2 KB
static/fragments/section/abstract.mdmarkdown1.7 KB
static/fragments/section/conclusion.mdmarkdown929 B
static/fragments/section/discussion.mdmarkdown1.8 KB
static/fragments/section/experiments.mdmarkdown3.0 KB
static/fragments/section/intro.mdmarkdown2.6 KB
static/fragments/section/method.mdmarkdown1.5 KB
static/fragments/section/related-work.mdmarkdown1.2 KB
static/fragments/section/title.mdmarkdown999 B
static/fragments/task/manuscript.mdmarkdown288 B
static/fragments/task/submission-package.mdmarkdown2.5 KB
templates/submission/declarations-and-reviewers.texother2.6 KB
templates/submission/highlights-and-summary.texother1.1 KB
templates/submission/initial-cover-letter.texother1.6 KB
templates/submission/title-page.texother1.9 KB
tests/scoped-drafting.mdmarkdown1.9 KB

references/method.md

View on GitHub
# Method Writing Guide

## Contents

- [Goal](#goal)
- [Pre-Writing Questions](#pre-writing-questions)
- [Method Writing Steps](#method-writing-steps)
- [Three Elements of a Pipeline Module](#three-elements-of-a-pipeline-module)
- [Method Content Decomposition](#method-content-decomposition)
- [How to Write Module Design](#how-to-write-module-design)
- [How to Write Module Motivation](#how-to-write-module-motivation)
- [How to Check Whether Method is Easy to Understand](#how-to-check-whether-method-is-easy-to-understand)
- [Method Section Skeleton](#method-section-skeleton)
- [Overview Subsection](#overview-subsection)
- [Section 3.1 and Other Module Subsections](#section-31-and-other-module-subsections)
- [Module Writing Pattern (Mermaid)](#module-writing-pattern-mermaid)
- [Implementation Details](#implementation-details)
- [Example Bank](#example-bank)


## Goal

Write the Method section clearly by following this sequence:

1. Answer key method-design questions.
2. Draw a pipeline figure sketch.
3. Write the method section step by step.

## Pre-Writing Questions

`Before writing Method, first answer: (1) what modules exist in the method, and (2) for each module, what is the workflow, why this module is needed, and why this module works.`

Recommended organization:

1. List all modules in the pipeline.
2. For each module, answer three questions:

- How does the module run?
- Why do we need this module?
- Why does this module work?

3. Organize answers as a mind map or a table for clarity.

## Method Writing Steps

`Method writing steps: (1) draw pipeline figure sketch, (2) map subsections from the sketch, (3) plan each subsection with motivation/design/advantages, (4) write module design first, (5) then add motivation and technical advantages.`

Step-by-step workflow:

1. Draw the pipeline figure sketch.
2. Use the sketch to organize Method subsection structure.
3. For each subsection, plan three parts: motivation, module design, and technical advantages.
4. Write module design first to build a concrete backbone.
5. Add motivation and technical advantages afterward.

## Three Elements of a Pipeline Module

`A pipeline module has three elements: Module design, Motivation of this module, and Technical advantages of this module.`

### 1) Module Design

Definition:

1. Describe representation/network/data-structure details.
2. Describe the forward process clearly: given input -> step 1 -> step 2 -> step 3 -> output.

### 2) Motivation of This Module

Definition:

1. Explain why this module is needed.
2. Use problem-driven logic: because problem X exists, we design module Y.

### 3) Technical Advantages of This Module

Definition:

1. Explain why this module has technical advantage over alternatives.
2. Tie advantage to measurable behavior when possible.

### Example of the Three Elements

Local cite:

1. `references/examples/method/example-of-the-three-elements.md`

## Method Content Decomposition

```mermaid
flowchart LR
    A["Draw the technical pipeline figure"] --> B["Decompose Method content"]
    B --> C1["Subsection 1 (Technical Module 1)"]
    B --> C2["Subsection 2 (Technical Module 2)"]
    B --> C3["Subsection 3 (Technical Module 3)"]
    C1 --> D1["Motivation"]
    C1 --> D2["Detailed design"]
    C1 --> D3["Technical advantage"]
```

## How to Write Module Design

`Module design usually has two parts: (1) describe specific data/network structures, and (2) describe forward process as input -> steps -> output.`

Writing structure:

1. Define key structures first (representation, network, data structure).
2. Write forward process in strict execution order.
3. End with output interpretation or purpose.

Sentence skeleton:

1. `We represent ... with ...`
2. `Given [input], we first ... then ... finally ...`
3. `This produces [output], which is used for ...`

Local cite:

1. `references/examples/method/module-design-instant-ngp.md`

## How to Write Module Motivation

`Module motivation is usually problem-driven: because a problem exists, we design xx to solve it.`

Typical opening sentences:

1. `A remaining problem/challenge is ...`
2. `However, we ...`
3. `Previous methods have difficulty in ...`

Local cite:

1. `references/examples/method/module-motivation-patterns.md`

## How to Check Whether Method is Easy to Understand

`Check method clarity from three levels: writing logic, paragraph writing, and sentence writing.`

### 1) Logic-level check

1. After finishing the paper, summarize the Method writing logic again.
2. Check whether this summarized logic is smooth and easy to follow.

### 2) Paragraph-level check

1. The first sentence of each paragraph should make readers immediately understand what this paragraph is about.
2. One paragraph should clearly deliver one message.

### 3) Sentence-level check

1. Carefully check whether the **motivation** of each sentence is explicit. Keep one thing clear to readers at all times: **why this sentence content is needed**.
2. Carefully check sentence-to-sentence flow.
3. Carefully check term consistency and avoid changing key terms back and forth.

## Method Section Skeleton

```latex
\section{Method}
% Overview
% Section 3.1
% Section 3.2
% Section 3.3
```

Local cite:

1. `references/examples/method/section-skeleton.md`

## Overview Subsection

`Overview should usually include: setting, core contribution, optional pipeline figure pointer, and a map of what each subsection contains.`

Writing structure:

1. One to two sentences for task setting.
2. One to two sentences for core contribution.
3. If pipeline/framework is novel, point to overview figure.
4. Tell readers what Section 3.1/3.2/3.3 covers.

Local cite:

1. `references/examples/method/overview-template.md`

## Section 3.1 and Other Module Subsections

`Basic subsection logic: (1) motivation of this module, (2) module forward process/module design, (3) technical advantages of this module.`

Local cite:

1. `references/examples/method/example-of-the-three-elements.md`

## Module Writing Pattern (Mermaid)

```mermaid
flowchart TB
    M1["State module motivation (challenge)"] --> M2["Define module design (representation/network)"]
    M2 --> M3["Describe forward process (input -> steps -> output)"]
    M3 --> M4["Explain technical advantages and verifiable gains"]
```

## Implementation Details

`Implementation details include hyperparameters (e.g., layer count, feature dimensions), coordinate transforms/normalization, and other practical details. Put them near the end of Method or in a dedicated Implementation Details section.`

## Example Bank

1. `references/examples/method-examples.md`
2. `references/examples/method/pre-writing-questions.md`
3. `references/examples/method/module-triad-neural-body.md`
4. `references/examples/method/module-design-instant-ngp.md`
5. `references/examples/method/module-motivation-patterns.md`
6. `references/examples/method/section-skeleton.md`
7. `references/examples/method/overview-template.md`
8. `references/examples/method/example-of-the-three-elements.md`
9. `references/examples/method/method-writing-common-issues-note.md`
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall