ljg-book: Book Teardown
Input a book, output its core framework.
What is Book Teardown
It’s not a book review, not a chapter summary, not praise—it’s pulling out the author’s core framework and laying it out on the table.
It’s easy to get lost in an author’s writing style while reading. Book teardown means stepping out of that style to see the author’s "viewfinder." Only when you understand the viewfinder can you truly understand the whole book.
Five Key Points
Ask each question separately, then string the answers together.
1. Core Question
What is the author really answering? This is a question, not a topic.
A topic could be "free will"—the question would be "Does free will actually exist, or do we just think it does?"
A topic is a topic. A question is a question.
The question must be sharp—it’s the itch that bothered the author before they even started writing the book. The book is the answer; the question is the itch.
How to find it: Read the author’s introduction/preface, look for the sentence that starts with "I wrote this book to..." If you can’t find it, look for the point the author keeps returning to—the thing they can’t shake off even after hundreds of pages, that’s the core question.
2. Fundamental Assumptions
What unproven foundations does the author stand on?
Every book has a few "ceilings"—the author doesn’t prove them, they rely on them to build their argument. Shake any one of them, and the whole book collapses.
Use two operational questions to analyze the book:
- What is off-limits to question in this book? (Asking it would get you labeled an outsider by the author)
- What must the author believe to keep writing? (Without it, all subsequent arguments lose their foundation)
The answers to these are the book’s fundamental assumptions.
Present them without elaboration. These assumptions don’t need proof—just lay them out; proving them isn’t the teardown’s job.
3. Analytical Framework
What lens does the author use to see the world?
Every author has a viewfinder. Darwin’s viewfinder is "variation + selection + time"—he looks at butterflies, humans, and tribes through this lens. Marx’s viewfinder is "relations of production determine superstructure"—he looks at history, society, and art through this lens. Freud’s viewfinder is "consciousness is just the tip of the iceberg; the unconscious is the real protagonist"—he looks at dreams, slips of the tongue, and politics through this lens.
How to find the author’s lens: What tool do they repeatedly use? What angle do they always take? When they see X, their first thought is Y—that Y is their lens.
The lens doesn’t have to be a noun. It can be an action ("reduce to root cause"), a distinction ("natural state vs. cultural state"), or a contrast ("explicit logic vs. implicit structure").
Be ruthless when defining the lens—explain it in one sentence, not an entire chapter.
4. Core Argument / Conclusion
What did the author ultimately conclude?
It’s not "how many examples they cited" or "how many arguments they made." It’s: when you close the book, what is the one thing the author wants you to take away?
It’s usually just one or two sentences.
Test: If you extract this sentence out of the author’s context, does it still hold weight? If it’s just repeating the book’s title, that’s not a core argument—it’s a label. If it’s just a cliché ("things are dialectical" "everything is connected"), that’s empty talk.
The core argument must be sharp—it must stand on its own, be debatable, and quotable.
No weak statements. "The author believes human nature is complex" is weak—what isn’t complex?
5. God’s-Eye Compression
The entire book is hundreds of pages; from a god’s-eye view, what does it compress into a few sentences?
It’s not an abstract—abstracts are the author’s own product introduction. God’s-eye compression is you standing above the author and seeing: what is the author really saying?
Three to five sentences are enough. Each sentence must pick a load-bearing beam—one on fundamental assumptions, one on analytical framework, one on core argument, plus one or two sentences connecting to real-world implications.
After writing, ask yourself: Can someone who hasn’t read the book say they roughly know what the book is about after reading these sentences? If yes → pass.
How to Write
Calm, concise, sharp, straightforward.
Don’t praise the author, don’t criticize them, don’t defend them, don’t apologize for them.
Five numbered sections (1-5). Each section should flow smoothly, no detours.
Start each section with a topic sentence stating the core point. Then elaborate in two or three sentences. Don’t overuse bullet points—a single paragraph of prose is better than ten bullets.
Use short sentences. Cut prepositions. Avoid "through / by / relying on / based on X" whenever possible.
Use plain Chinese—similar to the style of Wang Zengqi, Wang Xiaobo, or A Cheng. After writing each section, read it aloud; if it feels awkward, rewrite the whole sentence (don’t just tweak words).
Complete anti-translation rules:
~/.claude/PAI/USER/AI_WRITING_PATTERNS.md
(must review Layer A).
Avoid academic jargon. Use "the author argued" "the author believes" sparingly—directly state what the author did. Eliminate all phrases like "X pointed out in Chapter N..."
How to Find Materials
If the user only provides a book title—
- First use WebSearch / WebFetch to find the author, introduction, table of contents, and secondary analyses of the core argument
- Answer only after obtaining the core argument
- Don’t teardown based on memory—memory-based teardowns result in Wikipedia-style empty talk
If the user provides a PDF / arxiv / content—read it directly, no need to search.
If it’s a classic book—you can use the LLM’s internal knowledge, but still ask yourself: Is this actually in the book, or did I make it up? Delete anything you made up.
Output
- Get timestamps: and
date "+%Y-%m-%d %a %H:%M"
- Write to
~/Documents/notes/{timestamp}--book-teardown-{book-title}__book.org
- Use org-mode format (titles use , bold uses single asterisks,禁止 markdown 双星号)
- File header:
#+TITLE: Book Teardown: 《{book-title}》
#+SUBTITLE: {author} | {one-sentence core argument}
#+DATE: [{YYYY-MM-DD Day HH:MM}]
#+FILETAGS: :book:{book-field e.g. philosophy/biology/economics}:
#+IDENTIFIER: {YYYYMMDDTHHMMSS}
- Five prose sections in the body, numbered 1-5.
- Report the file path to the user.
Red Lines (must follow every one)
- No praise, no criticism, no defense — The teardown stands above the author, not as a fan or opponent
- Calm, concise, sharp, straightforward — Read each section aloud without awkwardness
- Core argument cannot be weak — Eliminate weak statements ("X is complex")
- No elaboration on fundamental assumptions — Just present them
- God’s-eye compression ≤5 sentences — Each sentence is a load-bearing beam
- Zero academic jargon — Use "the author argued / believes / pointed out" sparingly
- Anti-translation style — Remove all Layer A marker words; after writing, ask: Would Wang Zengqi write this way?