Summarizing Books Markdown

Example

### Chapter Title

▼ **Sub-section Title**

* **Primary Key Point**: Capturing a high-level technical concept.
    * **Specific Nuance**: Explaining the "why" and "how" behind the point.
    * **Critical Exception**: Noting any important corner cases.
* `code_snippet` for practical application.

Common Mistakes

• Oversimplification: Ignoring the technical "why" or "how" mentioned in the source text.
• Marker mismatch: Using ▽ instead of ▼.
• Nesting errors: Putting ### under ▼. (Hierarchy: ### -> ▼ -> *).
• Missing context: Failing to include the specific tools, commands, or parameters mentioned in the text.

Red Flags - STOP and Start Over

• Surface-level or vague summaries: If the summary lacks technical depth or ignores specific "how-to" details.
• The final summary is less than one third of the original
• Using # or ## for chapter headings.
• Omitting the ▼ marker for sub-sections.
• Writing long paragraphs instead of concise, detailed bullet points.