ljg-plain

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

ljg-plain: 白

ljg-plain: Bai

让人 grok。

不规定怎么写。规定不能怎么写。下限锁死，上限放开。不同主题有不同的最佳写法——类比、故事、问答、递进的例子、一个长场景——由内容决定形式。

Make it grokkable.

No fixed writing format. Only rules about what NOT to do. Lock the bottom line, leave the upper limit open. Different topics call for different best approaches — analogies, stories, Q&A, progressive examples, a long scenario — form is determined by content.

格式约束

Format Constraints

Org-mode 语法

Org-mode Syntax

加粗用
```
*bold*
```
（单星号），禁止
```
**bold**
```
标题层级从
```
*
```
开始，不跳级

Use
```
*bold*
```
(single asterisk) for bold text;
```
**bold**
```
is prohibited
Heading levels start with
```
*
```
, no skipping levels

ASCII Art

所有图表用纯 ASCII 字符。允许：

+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' "

和空格。禁止 Unicode 绘图符号。

All diagrams must use pure ASCII characters. Allowed characters:

+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' "

and spaces. Unicode drawing symbols are prohibited.

Denote 文件规范

Denote File Specifications

时间戳：
```
date +%Y%m%dT%H%M%S
```
可读时间：
```
date "+%Y-%m-%d %a %H:%M"
```

文件名：

{时间戳}--plain-{简短标题}__plain.org

输出目录：
```
~/Documents/notes/
```

Timestamp:
```
date +%Y%m%dT%H%M%S
```
Human-readable time:
```
date "+%Y-%m-%d %a %H:%M"
```

Filename:

{timestamp}--plain-{short-title}__plain.org

Output directory:
```
~/Documents/notes/
```

Org 文件头

Org File Header

#+title:      plain-{简短标题}
#+date:       [{YYYY-MM-DD Day HH:MM}]
#+filetags:   :plain:atom:
#+identifier: {YYYYMMDDTHHMMSS}
#+source:     {URL 或来源描述}

文件写入后报告路径。

#+title:      plain-{short-title}
#+date:       [{YYYY-MM-DD Day HH:MM}]
#+filetags:   :plain:atom:
#+identifier: {YYYYMMDDTHHMMSS}
#+source:     {URL or source description}

Report the file path after writing.

红线（每条必须过，顺序即优先级）

Red Lines (Must Follow in Order of Priority)

口语检验 — 最高法则。读出声来，你会这样跟一个聪明的朋友说话吗？不会→改到会。连词不是敌人——"但是""所以"是思维转弯的声音，只砍机械连词（"此外""值得注意的是"）
零术语 — 聪明的 12 岁孩子能复述。专业词必须出现时，先用大白话把意思落地，再顺带提术语名
短词优先 — 能用两个字说的不用四个字。「进行分析」→「看」。大词不让你显得聪明，只让人读得累
一句一事 — 每句只推进一步。长句拆短
具体 — 名词看得见，动词有力气。「有人觉得情况不太好」→「张三说项目要黄了」。形容词能砍就砍
开头给理由 — 第一句话让人想读下一句。不铺垫、不背景、不「自古以来」
不填充 — 删开场白、拐杖词、夸大象征。每句都在干活
信任读者 — 跳过软化、辩解、手把手引导。说一遍够了
诚实 — 想不清楚就说想不清楚。"大概 70%" 比"可能"诚实

Spoken Language Test — Supreme Rule. Read it aloud: would you talk to a smart friend like this? If not, revise until you would. Conjunctions are not enemies—"but" and "so" reflect shifts in thinking; only cut mechanical conjunctions like "furthermore" or "it is worth noting that"
Zero Jargon — A smart 12-year-old can retell it. If technical terms must be used, first explain the concept in plain language, then mention the term
Prefer Short Words — Use two-character words instead of four when possible. "Conduct an analysis" → "look into it". Big words don’t make you look smart—they just tire readers out
One Idea per Sentence — Each sentence only advances the content one step. Split long sentences into short ones
Be Specific — Nouns should be visual, verbs should be strong. "Some people think the situation is not good" → "Zhang San says the project is going to fail". Cut adjectives whenever possible
Lead with a Reason — The first sentence should make readers want to keep reading. No setup, no background, no "since ancient times"
No Filler — Cut opening remarks, crutch words, and overblown metaphors. Every sentence must serve a purpose
Trust the Reader — Skip softeners, justifications, and hand-holding explanations. Say it once and it’s enough
Be Honest — If you’re unsure, say so. "About 70%" is more honest than "maybe"

工具箱（选用，不必全用）

Toolkit (Optional, No Need to Use All)

写的时候可以从这里拿工具，没有哪个是必须的：

类比 — 找结构对得上的日常经验。好类比承重（去掉它文章塌），多层（挖一层还像），自明（不需要解释类比本身）。动词延伸到新对象时检查中文动宾搭配是否自然
好问题 — 找读者的卡点，变成问题。读者被卡住，才想往下读
裂缝 — 模型/类比在哪里不够？那个点往往最值钱。不宣布它，让读者自己感到
画面 — 闭眼能看到的场景。硬造的画面比没有更糟
故事 — 一个具体的人遇到一个具体的问题。读者跟着走
反问入链 — 遇到隐含前提，用问题打开，然后回答它
骨架图 — 概念涉及空间关系时，嵌入 ASCII 图（
```
#+begin_example
```
块）

You can pick tools from here when writing; none are mandatory:

Analogy — Find daily experiences with matching structures. A good analogy is foundational (the article falls apart without it), multi-layered (it still makes sense when you dig deeper), and self-explanatory (no need to explain the analogy itself). Check if the verb-object collocation is natural in Chinese when extending verbs to new objects
Good Questions — Identify readers’ sticking points and turn them into questions. Readers keep reading when they’re stuck on something
Cracks — Where does the model/analogy fall short? That spot is often the most valuable. Don’t point it out explicitly—let readers feel it themselves
Mental Images — Scenes that readers can picture in their minds. Forced images are worse than none
Story — A specific person facing a specific problem. Readers follow along
Rhetorical Question Chain — When encountering implicit assumptions, use questions to unpack them, then answer
Skeleton Diagrams — Embed ASCII diagrams (in
```
#+begin_example
```
blocks) when concepts involve spatial relationships

执行

Execution

1. 获取内容

1. Obtain Content

URL → WebFetch | 文本 → 直接用 | 文件路径 → Read | 概念 → 直接解释 | 书名/论文名 → WebSearch

URL → WebFetch | Text → Use directly | File path → Read | Concept → Explain directly | Book/paper title → WebSearch

2. 写

2. Write

形式自由。从工具箱里选最适合这个主题的方式，也可以不选——如果有更好的写法，用它。

输出是一篇从第一行流到最后一行的连贯文章。全文只有文件标题，正文无子标题。

禁止：

结构标签（
```
* 类比
```
/
```
* 裂缝
```
等）
指向写作过程的元评论（「打个比方」「接下来我们讨论」）

Form is free. Choose the most suitable tool from the toolkit for the topic, or use a better method if you have one.

The output should be a coherent article that flows from start to finish. The full text only has a file title—no subheadings in the main body.

Prohibited:

Structural labels (e.g.,
```
* Analogy
```
/
```
* Cracks
```
)
Meta-comments about the writing process (e.g., "to put it another way" / "next we’ll discuss")

3. 过红线

3. Check Against Red Lines

逐条扫红线清单。额外检查：

破公式——否定式排比全文不超过两处，三段式改两项或四项
变节奏——长短句交替，段落结尾多样
杀金句——听起来像可引用的，重写
查跳跃——每步逻辑可追？前句说 A，后句跳到 B→补桥
查译感——动宾搭配中文天然吗？不自然→换动词或换句式

扫完列修改清单（哪句触发什么，改前→改后）。清单不写入文件。

Go through the red line checklist one by one. Additional checks:

Break Formulas — No more than two negative parallel structures in the entire text; rewrite three-part structures into two or four parts
Vary Rhythm — Alternate long and short sentences; vary paragraph endings
Kill Catchphrases — Rewrite any lines that sound quotable
Check for Leaps — Is each logical step traceable? If the previous sentence talks about A and the next jumps to B → fill the gap
Check for Translation Feel — Is the verb-object collocation naturally Chinese? If not → change the verb or sentence structure

After checking, make a revision list (which line triggered which rule, before → after). Do not include the list in the file.

4. 生成 Org 文件

4. Generate Org File

按 Denote 规范获取时间戳，写出文件头 + 正文，存入

~/Documents/notes/

。

Get the timestamp per Denote specifications, write the file header + main body, and save it to

~/Documents/notes/

验收

Acceptance Criteria

Grok：读完能用自己的话复述核心
零术语：12 岁孩子能跟上
记得住：读完脑子里留下了什么——一个画面、一个问题、一个转折，什么都行
想读完：从头到尾没有想跳过的段落

Grok: Readers can retell the core content in their own words after reading
Zero Jargon: A 12-year-old can follow along
Memorable: Readers retain something after reading—a mental image, a question, a twist, anything works
Engaging: No paragraphs make readers want to skip ahead