ljg-plain
lijigang/ljg-skills
Rewrite any content so a smart 12-year-old understands it—plain language, no jargon.
What is ljg-plain?
ljg-plain rewrites content in plain language that a smart 12-year-old can grasp. It enforces zero jargon, short words, concrete examples, and conversational tone—form follows content, not templates. Use it when asked to explain something plainly ('白话说', 'plain', 'grok', etc.).
- Rewrites technical or complex content into conversational language a 12-year-old can follow
- Enforces zero jargon—technical terms only appear after plain-language explanation
- Generates Org-mode files with Denote naming convention and metadata
- Uses ASCII art only for diagrams; no Unicode symbols
- Applies nine red-line rules: oral test, zero jargon, short words, one-idea-per-sentence, concrete nouns/verbs, strong openings, no filler, trust the reader, honesty
How to install ljg-plain
npx skills add https://github.com/lijigang/ljg-skills --skill ljg-plainHow to use ljg-plain
- 1.Invoke the skill when you need plain-language rewriting (e.g., 'plain', '白话说', 'grok', 'explain')
- 2.Provide the content: a URL, text, file path, or concept name
- 3.The skill fetches/reads the content, then rewrites it following the nine red-line rules
- 4.Review the output Org file saved to ~/Documents/notes/ with Denote naming
- 5.Check that it passes the four verification criteria: grok-able, zero jargon, memorable, readable end-to-end
Use cases
- Simplify technical documentation or research papers for general audiences
- Explain complex concepts (algorithms, finance, science) to non-experts
- Rewrite internal memos or reports to be actually readable
- Turn abstract ideas into concrete, memorable explanations
- Create plain-language versions of policy or legal content
- Technical writers simplifying documentation
- Educators explaining difficult concepts
- Anyone needing to communicate complex ideas clearly
- Teams writing for mixed-expertise audiences
ljg-plain FAQ
Nine mandatory rules in priority order: oral test (would you say it aloud?), zero jargon, short words, one idea per sentence, concrete language, strong opening, no filler, trust the reader, honesty. Every output must pass all nine.
No. The output is one continuous article with only the file title as a heading. No subsection labels, no meta-commentary about the writing process.
Introduce the term after explaining it in plain language first. Example: 'The computer learns patterns from examples—this is called machine learning.'
~/Documents/notes/ as an Org file following Denote naming: {YYYYMMDDTHHMMSS}--plain-{short-title}__plain.org
One where the structure matches, it works on multiple levels, and it doesn't need explanation itself. If you have to explain the analogy, it's not good enough.
Full instructions (SKILL.md)
Source of truth, from lijigang/ljg-skills.
name: ljg-plain description: "Cognitive atom: Plain (白). Rewrites any content so a smart 12-year-old groks it. Structure-free — form follows content. Use when user says '白话说', '说人话', '解释一下', 'plain', 'grok'." user_invocable: true version: "5.0.0"
ljg-plain: 白
让人 grok。
不规定怎么写。规定不能怎么写。下限锁死,上限放开。不同主题有不同的最佳写法——类比、故事、问答、递进的例子、一个长场景——由内容决定形式。
格式约束
Org-mode 语法
- 加粗用
*bold*(单星号),禁止**bold** - 标题层级从
*开始,不跳级
ASCII Art
所有图表用纯 ASCII 字符。允许:+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' " 和空格。禁止 Unicode 绘图符号。
Denote 文件规范
- 时间戳:
date +%Y%m%dT%H%M%S - 可读时间:
date "+%Y-%m-%d %a %H:%M" - 文件名:
{时间戳}--plain-{简短标题}__plain.org - 输出目录:
~/Documents/notes/
Org 文件头
#+title: plain-{简短标题}
#+date: [{YYYY-MM-DD Day HH:MM}]
#+filetags: :plain:atom:
#+identifier: {YYYYMMDDTHHMMSS}
#+source: {URL 或来源描述}
文件写入后报告路径。
红线(每条必须过,顺序即优先级)
- 口语检验 — 最高法则。读出声来,你会这样跟一个聪明的朋友说话吗?不会→改到会。连词不是敌人——"但是""所以"是思维转弯的声音,只砍机械连词("此外""值得注意的是")
- 零术语 — 聪明的 12 岁孩子能复述。专业词必须出现时,先用大白话把意思落地,再顺带提术语名
- 短词优先 — 能用两个字说的不用四个字。「进行分析」→「看」。大词不让你显得聪明,只让人读得累
- 一句一事 — 每句只推进一步。长句拆短
- 具体 — 名词看得见,动词有力气。「有人觉得情况不太好」→「张三说项目要黄了」。形容词能砍就砍
- 开头给理由 — 第一句话让人想读下一句。不铺垫、不背景、不「自古以来」
- 不填充 — 删开场白、拐杖词、夸大象征。每句都在干活
- 信任读者 — 跳过软化、辩解、手把手引导。说一遍够了
- 诚实 — 想不清楚就说想不清楚。"大概 70%" 比"可能"诚实
工具箱(选用,不必全用)
写的时候可以从这里拿工具,没有哪个是必须的:
- 类比 — 找结构对得上的日常经验。好类比承重(去掉它文章塌),多层(挖一层还像),自明(不需要解释类比本身)。动词延伸到新对象时检查中文动宾搭配是否自然
- 好问题 — 找读者的卡点,变成问题。读者被卡住,才想往下读
- 裂缝 — 模型/类比在哪里不够?那个点往往最值钱。不宣布它,让读者自己感到
- 画面 — 闭眼能看到的场景。硬造的画面比没有更糟
- 故事 — 一个具体的人遇到一个具体的问题。读者跟着走
- 反问入链 — 遇到隐含前提,用问题打开,然后回答它
- 骨架图 — 概念涉及空间关系时,嵌入 ASCII 图(
#+begin_example块)
执行
1. 获取内容
URL → WebFetch | 文本 → 直接用 | 文件路径 → Read | 概念 → 直接解释 | 书名/论文名 → WebSearch
2. 写
形式自由。从工具箱里选最适合这个主题的方式,也可以不选——如果有更好的写法,用它。
输出是一篇从第一行流到最后一行的连贯文章。全文只有文件标题,正文无子标题。
禁止:
- 结构标签(
* 类比/* 裂缝等) - 指向写作过程的元评论(「打个比方」「接下来我们讨论」)
3. 过红线
逐条扫红线清单。额外检查:
- 破公式——否定式排比全文不超过两处,三段式改两项或四项
- 变节奏——长短句交替,段落结尾多样
- 杀金句——听起来像可引用的,重写
- 查跳跃——每步逻辑可追?前句说 A,后句跳到 B→补桥
- 查译感——动宾搭配中文天然吗?不自然→换动词或换句式
扫完列修改清单(哪句触发什么,改前→改后)。清单不写入文件。
4. 生成 Org 文件
按 Denote 规范获取时间戳,写出文件头 + 正文,存入 ~/Documents/notes/。
验收
- Grok:读完能用自己的话复述核心
- 零术语:12 岁孩子能跟上
- 记得住:读完脑子里留下了什么——一个画面、一个问题、一个转折,什么都行
- 想读完:从头到尾没有想跳过的段落
Related skills
More from lijigang/ljg-skills and the wider catalog.
ljg-travel
Deep cultural travel research: auto-generate structured org-mode documents and reference cards for museums and ancient architecture.
ljg-card
Transform content into styled PNG visuals with seven layout molds—long cards, infographics, comics, sketchnotes, whiteboards, and more.
ljg-roundtable
Structured roundtable discussion framework with truth-seeking moderator and representative figures for multi-perspective debate.
ljg-paper
Reads research papers as continuous stories, extracting core propositions through narrative structure for non-academics.
ljg-learn
Deep concept anatomist that deconstructs ideas through 8 exploration dimensions and compresses insights into epiphany.
ljg-writes
Surgical writing engine: dissect an idea layer by layer into 1000-1500 word critical essays.