SuperAPI AI Directory

ljg-plain

General & other

View repository

Updated 10-16 00:00

About this skill

ljg-plain: 白

Make people grok.

It doesn't dictate how to write. It dictates how not to write. The floor is locked down, the ceiling is open. Different topics have different best ways of writing — analogy, story, Q&A, progressive examples, one long scene — the content decides the form.

Format constraints

Org-mode syntax

  • Bold uses *bold*(single asterisk), forbidden **bold**
  • Heading levels start from * , no skipping levels

ASCII Art

All diagrams use pure ASCII characters. Allowed:+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' " and spaces. Unicode drawing symbols are forbidden.

Denote file conventions

  • Timestamp:date +%Y%m%dT%H%M%S
  • Readable time:date "+%Y-%m-%d %a %H:%M"
  • Filename:{时间戳}--plain-{简短标题}__plain.org
  • Output directory:~/Documents/notes/

Org file header

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

Report the path after the file is written.

Red lines (every one must pass, order is priority)

  1. Read-aloud test — the highest law. Read it out loud, would you talk to a smart friend like this? No → revise until yes. Conjunctions are not the enemy — "but" and "so" are the sound of thought turning, only cut mechanical conjunctions ("moreover", "it is worth noting that")
  2. Zero jargon — a smart 12-year-old can retell it. When a technical term must appear, first land the meaning in plain language, then mention the term name in passing
  3. Short words first — if you can say it in two characters, don't use four. "Conduct an analysis" → "look". Big words don't make you look smart, they just make people tired reading
  4. One thing per sentence — each sentence advances only one step. Split long sentences short
  5. Concrete — nouns you can see, verbs with force. "Someone feels the situation isn't great" → "Zhang San says the project is about to tank". Cut adjectives whenever you can
  6. Give the reason at the start — the first sentence makes people want to read the next. No setup, no background, no "since ancient times"
  7. No filler — delete opening pleasantries, crutch words, exaggerated symbolism. Every sentence is doing work
  8. Trust the reader — skip softening, justifying, hand-holding. Saying it once is enough
  9. Honest — if you can't think it through, say you can't think it through. "About 70%" is more honest than "possibly"

Toolbox (optional, no need to use all)

When writing you can take tools from here, none are mandatory:

  • Analogy — find everyday experience with matching structure. A good analogy bears load (remove it and the piece collapses), has layers (dig one layer and it still holds), is self-evident (no need to explain the analogy itself). When a verb extends to a new object, check whether the Chinese verb-object collocation is natural
  • Good question — find where the reader gets stuck, turn it into a question. Only when the reader is stuck do they want to read on
  • Crack — where does the model/analogy fall short? That point is often the most valuable. Don't announce it, let the reader feel it themselves
  • Image — a scene you can see with your eyes closed. A forced image is worse than none
  • Story — a specific person meets a specific problem. The reader follows along
  • Rhetorical question as entry link — When encountering an implicit premise, open with a question, then answer it
  • Skeleton diagram — When the concept involves spatial relationships, embed an ASCII diagram (#+begin_example blocks)

Execution

1. Get the content

URL → WebFetch | text → use directly | file path → Read | concept → explain directly | book title/paper title → WebSearch

2. Write

The form is free. Pick the approach from the toolbox that best suits this topic, or don't pick one—if there's a better way to write it, use that.

The output is a coherent piece of writing that flows from the first line to the last. The entire text has only the file title, and the body has no subheadings.

Prohibited:

  • Structural labels (* 类比 / * 裂缝 , etc.)
  • Meta-commentary pointing to the writing process ("for example" "next we'll discuss")

3. Pass the red lines

Scan the red-line checklist item by item. Additional checks:

  • Break the formula—no more than two instances of negative parallelism in the whole text; change three-part structures into two or four items
  • Vary the rhythm—alternate long and short sentences, diversify paragraph endings
  • Kill the catchy lines—rewrite anything that sounds quotable
  • Check for jumps—can every step of the logic be traced? The previous sentence says A, the next jumps to B → add a bridge
  • Check for translationese—are the verb-object collocations natural in Chinese? If not → change the verb or change the sentence pattern

After scanning, list the revisions (which sentence triggered what, before → after). The list is not written into the file.

4. Generate the Org file

Get the timestamp according to the Denote specification, write the file header + body, and save to ~/Documents/notes/。

Acceptance

  • Grok: after reading, you can restate the core in your own words
  • Zero jargon: a 12-year-old child can follow it
  • Memorable: after reading, something is left in your mind—an image, a question, a turn, anything works
  • Want to finish reading: from beginning to end, there is no paragraph you want to skip