Skip to content

Yuan1z0825/nature-skills / skills/nature-polishing

nature-polishing

Verified

Polish, translate, or tighten existing academic prose while preserving facts, terminology, and evidence boundaries. Use for 论文润色、学术翻译、正文精简, or manuscript LaTeX layout fixes. Use nature-writing when the main task is drafting new sections or rebuilding the manuscript argument.

static/fragments/section/discussion.md

View on GitHub
# Section: Discussion

Load `../../../../nature-shared/core/discussion-argument-language.md` for the
complete Discussion function chain, modality ladder, limitation logic, and
sentence-function audit.

Discussion should answer:

- how the work fits within the broader field
- what has been added to understanding
- who should be credited for earlier work
- whether the findings support, complicate, or revise earlier results
- how the findings are interpreted
- when that interpretation may fail

Begin with a brief central-finding anchor when needed, then synthesize across
Results claims. Do not replay the comparison, effect size, statistical test,
and inference used to demonstrate each claim.

Short rule:

- `Results = the evidence chain that establishes and advances claims`
- `Discussion = what those claims mean together, how they relate to the field,
  and when the synthesis may fail`

## Sentence syntax

Discussion sentences usually interpret:

- `may reflect`
- `suggests that`
- `could indicate`
- `is likely due to`
- `may facilitate`

Hedging strength should match evidence strength. Do not promote a "consistent with" finding to "demonstrates" wording.

## Common failure modes

- Re-summarizing Results instead of interpreting them.
- Skipping rival explanations.
- Omitting boundaries: when does the interpretation stop holding?
- Expanding from a narrow result to a field-wide implication without an
  evidence bridge.
- Stacking hedges or using `must`, `cannot`, `demonstrates`, or causal verbs
  more strongly than the design permits.
- Naming a limitation without stating its consequence for a claim or scope.
- Offering generic future work that does not resolve an identified uncertainty.
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: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated 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: 196kUpdated Claude CodeCodexVerifiedInstall