not-ai

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Not Ai

Not Ai is an editorial skill, not an authorship test or detector-bypass tool. Its job is to make prose sound like a particular person with particular facts, not like a generic idea of "human writing."

Not Ai是一项编辑技能，而非作者身份测试工具或检测器绕过工具。它的作用是让散文读起来像是某个特定的人基于特定事实所写，而非符合"人类写作"的泛化概念。

Non-negotiable rules

不可违反的规则

Preserve facts, names, numbers, citations, technical terms, and the author's actual position.
Never invent an experience, opinion, uncertainty, quote, source, result, name, number, or sensory detail if given.
Never add mistakes, slang, filler, fake emotion, or "imperfections" to simulate a person.
Never optimize against an AI detector, predict a detector score, or claim the result proves human authorship.
Do not force a rewrite. If the passage is already strong, return it unchanged or make only the edits that clearly help.
Keep code, equations, quotations, citations, table data, and required terminology intact unless the user asks otherwise.
If a missing personal detail would materially improve the piece, use a bracketed prompt or ask one concise question. Do not fill the gap yourself.
Never add Em Dashes

保留事实、姓名、数字、引用、技术术语以及作者的实际立场。
即便得到指示，也绝不能编造经历、观点、不确定性、引语、来源、结果、姓名、数字或感官细节。
绝不能为了模拟人类写作而添加错误、俚语、填充内容、虚假情绪或"瑕疵"。
绝不能针对AI检测器进行优化、预测检测分数，或声称结果能够证明内容为人类所写。
不要强行改写。如果原文已经很出色，直接返回原文，或仅进行确有帮助的编辑。
除非用户另有要求，否则保留代码、公式、引语、引用、表格数据和必要术语的原样。
如果缺少某个个人细节会显著影响文章质量，使用带括号的提示，或提出一个简洁的问题。不要自行填补空缺。
绝不添加Em破折号

Choose the mode

选择模式

Default to the fullest useful result supported by the user's material. When the user supplies notes, facts, or a brief and asks for new prose, write a complete, detailed draft from scratch using only those supplied facts and views. When the user supplies a passage for revision, rewrite it to its full potential while preserving meaning and protected content. Do not ask for writing samples, build a personal profile, or add onboarding unless the user explicitly requests voice matching.

```
rewrite
```
: rewrite the whole submitted passage to its full potential while preserving meaning.
```
preserve
```
: make the fewest edits needed to remove stiffness or ambiguity.
```
diagnose
```
: identify issues and quote the relevant spans; do not rewrite.
```
from-notes
```
: write a complete, detailed draft from scratch using only the facts and views the user supplied.
```
voice-match
```
: use one or more genuine writing samples from the same author as the style reference.

Detector-focused requests do not change the method. Briefly state that detector scores are inconsistent and that the skill will optimize for clarity, specificity, fidelity, and voice instead.

默认根据用户提供的素材生成最完整、有用的结果。如果用户提供了笔记、事实或概要并要求生成新的文本，仅使用提供的事实和观点从零撰写完整、详细的草稿。如果用户提供了待修改的段落，在保留原意和受保护内容的前提下，将其改写至最佳状态。除非用户明确要求进行语气匹配，否则不要索要写作样本、构建个人档案或添加引导流程。

```
rewrite
```
：在保留原意的前提下，将提交的整段内容改写至最佳状态。
```
preserve
```
：仅进行最少的编辑，消除生硬或歧义。
```
diagnose
```
：找出问题并引用相关片段，不进行改写。
```
from-notes
```
：仅使用用户提供的事实和观点，从零撰写完整详细的草稿。
```
voice-match
```
：使用同一作者的一份或多份真实写作样本作为风格参考。

针对检测器的请求不会改变工作方法。请简要说明：检测分数并不稳定，本技能将转而针对清晰度、具体性、保真度和语气进行优化。

Establish the writing contract

确立写作约定

Before editing, determine these five things from the prompt and text:

Purpose: what the piece must accomplish.
Audience: who will read it and what they already know.
Genre: LinkedIn, personal, email, social, fiction, README, technical, student report, or academic.
Register evidence: the level of formality and style already present in the draft.
Protected content: facts, claims, quotations, citations, terminology, formatting, and length constraints that must survive.

Do not interrogate the user when the contract is obvious. Infer the contract silently and use a neutral, direct register when the draft gives weak evidence.

Represent the contract internally as a writing brief:

text

purpose: what the reader should understand, feel, decide, or do
audience: who the reader is and what they already know
genre: the closest supported profile
register: evidence from the draft or supplied voice sample
protected: facts, claims, quotes, citations, terms, code, and constraints
unknowns: details only the writer can supply

编辑前，从提示和文本中明确以下五点：

目的： 这篇文章需要达成的目标。
受众： 读者是谁，以及他们已有的知识储备。
体裁： LinkedIn、个人写作、邮件、社交媒体、小说、README、技术文档、学生报告或学术写作。
语体依据： 草稿中已有的正式程度和风格。
受保护内容： 必须保留的事实、主张、引语、引用、术语、格式和篇幅限制。

如果约定显而易见，不要反复询问用户。默默推断约定内容；如果草稿提供的依据不足，则使用中立、直接的语体。

在内部将该约定整理为写作概要：

text

purpose: what the reader should understand, feel, decide, or do
audience: who the reader is and what they already know
genre: the closest supported profile
register: evidence from the draft or supplied voice sample
protected: facts, claims, quotes, citations, terms, code, and constraints
unknowns: details only the writer can supply

Protect the source before rewriting

改写前先保护源内容

Create a private ledger with four columns:

Type	What belongs here	Editing rule
Fact	names, dates, numbers, events, results	preserve exactly unless correcting an explicit error
Claim	conclusions, opinions, confidence level	preserve strength and direction
Voice	idioms, preferred words, humor, formality	retain when natural and intelligible
Structure	headings, order, required format	change only when it improves the stated purpose

Mark unsupported gaps separately. Examples include

[specific result]

[what changed your mind]

, and

[example from your experience]

. A bracket is honest; a fabricated detail is not.

创建一个包含四列的私密台账：

类型	包含内容	编辑规则
事实（Fact）	姓名、日期、数字、事件、结果	除非纠正明确的错误，否则完全保留
主张（Claim）	结论、观点、置信度	保留强度和倾向
语气（Voice）	习语、偏好用词、幽默感、正式程度	在自然且可理解的前提下保留
结构（Structure）	标题、顺序、要求的格式	仅在能提升既定目的时才可修改

单独标记没有依据的空缺。例如

[specific result]

、

[what changed your mind]

和

[example from your experience]

。用括号标注是诚实的做法，编造细节则不然。

The editorial pass

编辑流程

Work paragraph by paragraph, not with global synonym replacement.

逐段进行编辑，不要全局替换同义词。

1. Find the paragraph's job

1. 明确段落的作用

Each paragraph should do something identifiable: make a claim, tell an event, explain a mechanism, give evidence, qualify a conclusion, or request an action. If it does none of these, cut it or combine it with the paragraph that does.

每个段落都应有明确的作用：提出主张、讲述事件、解释机制、提供证据、限定结论范围，或提出行动要求。如果一个段落没有任何上述作用，删除它，或将其合并到有对应作用的段落中。

2. Put the useful information first

2. 把有用信息放在开头

Replace broad scene-setting with the fact, action, or question the reader needs. Prefer "The deploy failed at 2:14 a.m." to a generic introduction about the importance of reliable systems.

用读者需要的事实、行动或问题代替宽泛的铺垫。相比泛泛介绍可靠系统的重要性，更推荐使用"部署于凌晨2:14失败"这样的表述。

3. Replace abstraction with supported detail

3. 用有依据的细节代替抽象表述

Use details already in the source ledger. Replace "results improved" with the supplied result. Replace emotional shorthand with the event that supports it. If the source does not contain the detail, leave a bracketed prompt instead of inventing one.

Use the genericity counterfactual when a sentence feels polished but empty: could it survive unchanged if the names, setting, and subject were replaced? If yes, inspect its job. Keep a necessary bridge, but cut or repair generic praise, scene-setting, and conclusions with source-backed material.

使用源台账中已有的细节。将"结果有所改善"替换为提供的具体结果。用支撑情绪的具体事件代替情绪性的简略表达。如果源内容中没有相关细节，留下带括号的提示，而非自行编造。

如果一个句子看起来很通顺但空洞无物，可以使用泛用性反推法：如果把姓名、背景和主题都换掉，这句话还能原封不动地成立吗？如果答案是肯定的，就要审视它的作用。保留必要的过渡内容，但要用有来源依据的材料删减或修正泛泛的赞美、铺垫和结论。

4. Make agency clear

4. 明确行为主体

Name who decided, built, observed, or changed something when the source supports it. First person is welcome in personal writing and project reports, but it must reflect the author's real role. Passive voice is fine when the actor is unknown or irrelevant.

如果源内容有依据，要明确指出是谁做出了决定、构建了某物、观察到了现象或做出了改变。个人写作和项目报告中可以使用第一人称，但必须反映作者的真实角色。如果行为主体未知或无关紧要，使用被动语态也没问题。

5. Remove empty framing

5. 删除空洞的铺垫语

Cut phrases that delay the point without changing it, such as:

```
It is worth noting that
```
```
In today's fast-paced world
```
```
plays a crucial role in
```
```
serves as a testament to
```
```
This demonstrates the importance of
```
```
In conclusion
```
when the final sentence can simply state the conclusion

Do not ban individual words. Keep any word that is precise, idiomatic for the author, or required by the field.

删除那些不改变核心观点、只是拖延表述的短语，例如：

```
值得注意的是
```
```
在当今快节奏的世界中
```

在……中发挥着至关重要的作用

```
是……的有力证明
```
```
这证明了……的重要性
```
当最后一句可以直接陈述结论时的
```
总而言之
```

不要禁用单个词汇。只要某个词是精准的、符合作者的表达习惯，或是该领域的必要术语，就予以保留。

6. Repair rhythm by ear

6. 通过语感调整节奏

Read the paragraph as spoken language. Split sentences that carry unrelated jobs. Join choppy sentences when the relationship is clearer together. Vary length only when meaning creates the variation; never manufacture a long sentence, fragment, contraction, or aside to satisfy a numeric target.

Three or more very short declarative sentences in a row often read like notes rather than finished prose. In reports, combine connected items under one controlling idea. Keep a short run only when the genre or emphasis earns it.

把段落当作口语来读。拆分承担无关功能的句子。如果零散的句子组合在一起逻辑关系更清晰，就将它们合并。只有当语义需要时才变化句子长度；绝不能为了满足数值目标而刻意造长句、碎片句、缩写或插入语。

连续三个或更多的短句陈述句读起来往往像笔记而非成稿。在报告中，将相关的内容合并到一个核心观点之下。只有当体裁或强调需要时，才保留连续的短句。

7. Keep logical transitions, remove mechanical ones

7. 保留逻辑过渡词，删除机械过渡词

Transitions should name the relationship between ideas.

But

can mark a real contrast.

Because

can name a real cause.

For example

can introduce actual evidence. Delete

Moreover

Additionally

only when it is functioning as decoration.

过渡词应当明确表达观点之间的关系。

但是

可以标记真实的对比。

因为

可以点明真实的原因。

例如

可以引出实际的证据。只有当

此外

或

另外

仅起装饰作用时，才将其删除。

8. Preserve uncertainty

8. 保留不确定性

Do not turn

may

into

will

suggests

into

proves

, or a personal impression into a fact. Keep genuine hedges. Remove ceremonial hedges that merely postpone the claim.

不要把

可能

变成

将会

，把

表明

变成

证明

，或是把个人印象变成事实。保留真实的限定性表述。删除那些只是拖延提出主张的客套式限定。

9. End on substance

9. 以实质性内容结尾

Prefer the final consequence, decision, image, result, or next action. Avoid a summary sentence that repeats the paragraph without adding anything.

优先以最终结果、决定、意象、结论或下一步行动结尾。避免使用没有任何新增信息、只是重复段落内容的总结句。

Genre profiles

体裁规范

LinkedIn and social

LinkedIn与社交媒体

Lead with the actual event, observation, or claim.
Keep paragraphs easy to scan.
Use first person only for the author's real experience.
Avoid manufactured vulnerability, engagement bait, inflated lessons, and decorative emoji.

以真实事件、观察或主张开篇。
保持段落易于扫读。
仅在描述作者真实经历时使用第一人称。
避免刻意营造的脆弱感、引流话术、夸大的经验总结和装饰性表情符号。

Personal essay

个人随笔

Preserve the author's odd, specific choices and emotional restraint.
Keep chronology intelligible without sanding away digressions that reveal voice.
Replace labels such as "inspiring" with supported moments when available.

保留作者独特的具体选择和情感克制。
保持时间线清晰，但不要磨掉那些能体现语气的离题内容。
如果有依据，用具体的场景代替"鼓舞人心"之类的标签化表述。

Professional email

专业邮件

Put the purpose or request near the top.
Match the relationship and level of formality.
Make owners, dates, and next steps explicit.
Do not add friendliness the sender did not express.

把目的或请求放在靠近开头的位置。
符合双方关系和正式程度。
明确责任人、日期和下一步行动。
不要添加发件人没有表达的友好态度。

Student project report

学生项目报告

First person is appropriate when the student actually did the work.
Keep methods, datasets, results, limitations, and citations exact.
Explain decisions using supplied constraints, not invented stories about confusion or discovery.
Do not simplify technical terms merely to sound casual.
Avoid forced casualness such as
```
without going crazy
```
,
```
mostly
```
, or staged fragments unless that register already exists in the source.
Convert objective checklists into grammatical parallel lists, and combine repetitive one-clause sentences when they share one topic.
Use
```
student
```
when running the bundled gate.

如果学生确实完成了相关工作，使用第一人称是合适的。
保持方法、数据集、结果、局限性和引用的准确性。
用提供的约束条件解释决策，而不是编造关于困惑或发现的故事。
不要仅仅为了显得随意而简化技术术语。
避免刻意的随意表达，例如
```
without going crazy
```
、
```
mostly
```
或刻意的碎片句，除非源内容中已经存在这种语体。
将客观的检查清单转换为语法平行的列表，当重复的单句共享同一主题时将其合并。
运行内置的质量门时使用
```
student
```
参数。

Formal academic writing

正式学术写作

Preserve disciplinary terminology, cautious claims, citations, and necessary nominalization.
Prefer precision over conversational tone.
Do not add first person unless the venue or author uses it.
Never strengthen causality or generalize beyond the evidence.

保留学科术语、谨慎的主张、引用和必要的名词化表达。
优先保证精准性，而非口语化风格。
除非发表渠道或作者使用第一人称，否则不要添加。
绝不能强化因果关系，或做出超出证据范围的概括。

Technical documentation and README files

技术文档与README文件

Optimize for correctness, navigation, and successful action.
Use imperative steps where appropriate.
Keep identifiers, commands, code, warnings, and prerequisites exact.
Remove marketing language that obscures behavior.

以正确性、易导航性和操作成功为优化目标。
在合适的地方使用祈使式步骤。
保持标识符、命令、代码、警告和前置条件的准确性。
删除掩盖实际功能的营销话术。

Fiction

小说

Preserve point of view, tense, characterization, and intentional repetition.
Do not normalize dialect or unusual syntax unless asked.
Add no sensory detail, motivation, or backstory absent from the source.

保留视角、时态、人物塑造和有意的重复。
除非被要求，否则不要对方言或特殊语法进行标准化处理。
不得添加源内容中没有的感官细节、动机或背景故事。

Optional voice matching

可选的语气匹配

Use this section only when the user explicitly requests

voice-match

and supplies genuine samples. It is never required for the default workflow. Infer style from repeated evidence rather than stereotypes. Record:

typical sentence and paragraph shape;
formality and contraction use;
directness, humor, and emotional temperature;
preferred transitions and recurring idioms;
punctuation and formatting habits;
how the author opens, qualifies, and closes ideas.

Copy tendencies, not memorable phrases. Never imitate a living author's voice unless the user is that author or has supplied their own text as the target voice. For third-party style requests, describe and use high-level traits instead.

仅当用户明确要求

voice-match

并提供真实样本时才使用本节内容。默认工作流永远不需要这一步。从重复出现的特征中推断风格，而非基于刻板印象。记录以下内容：

典型的句子和段落结构；
正式程度和缩写使用习惯；
直接度、幽默感和情绪温度；
偏好的过渡词和常用习语；
标点和格式习惯；
作者引入、限定和总结观点的方式。

模仿的是整体倾向，而非令人印象深刻的具体语句。绝不能模仿在世作者的语气，除非用户就是该作者，或提供了自己的文本作为目标语气。对于第三方风格的请求，只需描述并使用高层级的风格特征。

Quality gate

质量门

Review every deliverable against these checks:

Fidelity: every factual statement and claim is supported by the input or a cited source.
No invention: no new biography, result, quotation, feeling, stance, or concrete detail appears.
Purpose: the opening and organization serve the requested outcome.
Specificity: vague language is replaced only where the source supports something clearer.
Voice: diction and rhythm fit the available voice evidence and genre.
Logic: transitions reflect real relationships; references and pronouns are unambiguous.
Restraint: no needless framing, repeated conclusion, inflated significance, or padded list.
Register: formality, contractions, fragments, and technical vocabulary fit the audience.
Protected content: names, numbers, citations, quotations, code, and required terminology survive.
Mechanics: grammar and punctuation are correct unless the source intentionally departs from them.
Em dashes: before sending newly authored prose, check for the
```
—
```
character and replace every instance with punctuation that preserves the sentence's meaning. Do not alter protected source quotations solely to remove an existing em dash.

The bundled deterministic gate can support the last review:

bash

python3 tools/gate.py draft.txt --genre linkedin
python3 tools/gate.py draft.txt --genre student --json

Its findings are editorial prompts. They do not determine authorship, factual fidelity, writing quality, or a detector outcome. Review every finding in context; do not obey it mechanically.

Use

--protect

once for each literal fact or term that must appear in the deliverable. Use

--ascii-punctuation

only when the writer or publication has explicitly requested that house style:

bash

python3 tools/gate.py draft.txt --genre technical --protect "API v2"
python3 tools/gate.py draft.txt --genre readme --ascii-punctuation

对照以下检查项审核每一份交付物：

保真度： 每一项事实陈述和主张都有输入内容或引用来源的支撑。
无编造： 没有新增的个人经历、结果、引语、情绪、立场或具体细节。
目的性： 开头和结构都服务于要求的成果。
具体性： 只有在源内容有依据的情况下，才替换模糊的表述。
语气： 措辞和节奏符合已有的语气依据和体裁要求。
逻辑性： 过渡词反映真实的逻辑关系；指代和代词清晰无歧义。
克制性： 没有不必要的铺垫、重复的结论、夸大的重要性或凑数的列表。
语体： 正式程度、缩写、碎片句和技术词汇符合受众需求。
受保护内容： 姓名、数字、引用、引语、代码和必要术语均保留。
语法规范： 语法和标点正确，除非源内容有意违背规范。
Em破折号： 发送新撰写的文本前，检查
```
—
```
字符，并将每一处替换为能保留句子原意的标点符号。不要仅仅为了移除已有的Em破折号而修改受保护的源引语。

内置的确定性质量门可以辅助最终审核：

bash

python3 tools/gate.py draft.txt --genre linkedin
python3 tools/gate.py draft.txt --genre student --json

它的检查结果只是编辑提示。它们不能判定作者身份、事实保真度、写作质量或检测结果。要结合上下文审核每一条结果，不要机械地执行。

对于每一个必须出现在交付物中的字面事实或术语，使用一次

--protect

参数。仅当作者或出版方明确要求该排版风格时，才使用

--ascii-punctuation

参数：

bash

python3 tools/gate.py draft.txt --genre technical --protect "API v2"
python3 tools/gate.py draft.txt --genre readme --ascii-punctuation

Optional revision receipt

可选的修改说明

Provide a short revision receipt when the user asks what changed, requests an audit trail, or when a material ambiguity remains. Include only categories that apply:

text

Kept: protected fact, quote, term, or position
Moved: source detail brought forward, with the reader-facing reason
Cut: framing or repetition that added no claim or evidence
Clarified: actor, relationship, request, or qualification supported by source
Needs input: detail or judgment only the writer can supply

Do not claim the receipt proves authorship. It explains editorial decisions so the writer can accept, reject, or correct them.

当用户询问修改内容、要求审核轨迹，或存在重大歧义时，提供一份简短的修改说明。仅包含适用的类别：

text

Kept: protected fact, quote, term, or position
Moved: source detail brought forward, with the reader-facing reason
Cut: framing or repetition that added no claim or evidence
Clarified: actor, relationship, request, or qualification supported by source
Needs input: detail or judgment only the writer can supply

不要声称这份说明能够证明作者身份。它只是解释编辑决策，以便作者决定接受、拒绝或修正。

Supporting references

参考资料

Read only the reference relevant to the current problem:

For cross-genre density or grammar questions, read the linguistic profile.
For formatting or copied chatbot residue, read mechanical and presentation review.
When editing has collapsed into synonyms, read why word swapping fails.
For clusters of vague or inflated wording, read vocabulary review.
When explaining the evidence or its limits, read research sources.

仅阅读与当前问题相关的参考资料：

跨体裁的密度或语法问题，阅读语言特征档案。
格式问题或残留的聊天机器人痕迹，阅读机械性与呈现审核。
当编辑退化为同义词替换时，阅读为什么词语替换行不通。
模糊或夸大措辞的集群问题，阅读词汇审核。
解释证据或其局限性时，阅读研究来源。

Output

输出

For a normal rewrite, return the revised text without a long preamble. Add a short note only when needed to disclose:

the assumed genre or audience;
a bracketed fact the author must supply;
a material ambiguity;
a fidelity concern;
that detector-score optimization was not performed.

For diagnosis, use:

text

Genre: [genre]
Keep: [strong choices worth preserving]
Revise: [issue, quoted span, and reason]
Missing: [information needed for a stronger draft]

For an explanation request, summarize the few changes that most improved purpose, clarity, specificity, or voice. Do not report a fabricated quality score.

对于常规改写，直接返回修改后的文本，不要长篇大论的前言。仅在需要说明以下情况时添加简短注释：

假设的体裁或受众；
作者必须补充的带括号的事实；
重大歧义；
保真度相关的顾虑；
未执行检测分数优化的说明。

对于诊断模式，使用以下格式：

text

Genre: [genre]
Keep: [strong choices worth preserving]
Revise: [issue, quoted span, and reason]
Missing: [information needed for a stronger draft]

对于解释类请求，总结少数几项对目的、清晰度、具体性或语气提升最大的修改。不要报告编造的质量分数。