A Technical Book Reading Companion for Source-Grounded Learning

Readers often get stuck for one of four reasons:

• Missing prerequisites: the author assumes knowledge you do not yet have.
• Compressed reasoning: several steps are packed into one paragraph or equation.
• Unclear scope: a rule works under conditions the reader has not noticed.
• Passive familiarity: a passage feels understandable until you try to explain or use it. The solution is not to ask AI for a replacement summary. It is to locate the exact gap, make it explicit, and test your understanding.

• “Explain this term using the vocabulary already introduced in the passage.”
• “How is this term different from [related term] in this chapter?”
• “Give a simple conceptual example, then state what the example leaves out.”
• “List the steps described here in causal order.”
• “What input, transformation, and output does this passage describe?”
• “Which step depends on an assumption that may not hold everywhere?”
• “What benefit and cost are being compared here?”
• “What would a practitioner need to measure before choosing this approach?”
• “Suggest a counterexample I could investigate outside the reader.”
• “Which claims in this passage could change over time?”
• “What should I verify in current official documentation?”
• “Separate the durable concept from version-specific details.” These prompts organize your checking. They do not make the response authoritative.