Begin with a reading purpose
A book summary for study is different from a publishing synopsis, a business brief, or a chapter-by-chapter reference. Decide whether the reader needs the central argument, the narrative arc, reusable concepts, character development, evidence, or an actionable framework. That decision controls what the summary should keep.
Normalize EPUB, MOBI, and ebook content
Electronic books often contain front matter, navigation files, repeated titles, footnotes, image captions, and publisher material. Preserve chapter boundaries and headings, but remove duplicate navigation and licensing text from the working copy. Note missing images or tables rather than pretending the text is complete.
Create a chapter map before a global summary
For each chapter, capture its purpose, main claim or event, key evidence, new terms or characters, and connection to the previous chapter. Keep these notes short. The map is not the final product; it is a control surface that prevents the model from overemphasizing the opening and conclusion.
Track argument and narrative differently
For nonfiction, follow the author’s thesis, supporting reasons, evidence, counterarguments, and implications. For fiction, track viewpoint, goals, conflict, change, causality, and theme. A plot list without character change is incomplete, while a theme statement without events may be unsupported.
Respect the author’s level of certainty
Words such as “may,” “suggests,” “demonstrates,” and “proves” are not interchangeable. Preserve the strength of the author’s claim, especially in history, science, policy, and business books. Separate the author’s position from the summarizer’s interpretation or critique.
Build a layered book summary
- A two-sentence premise for quick orientation.
- Five to ten core ideas or turning points.
- A chapter map for reference.
- Key terms, people, examples, or quotations to revisit.
- Questions, limitations, and possible applications.
Avoid common book-summary failures
Do not compress every chapter to the same length when some chapters carry more of the argument. Do not replace the author’s examples with generic ones. Do not present a critique as though it were part of the book. And do not rely on memory after processing a long file; keep the chapter map available during synthesis.
Next steps
Use the book summary prompt pattern to generate consistent chapter notes, then apply the verification checklist to names, dates, claims, and conclusions.