ai newsDo., 15. Okt.
EilmeldungMeta and Apple team up to make Muse AI models run better on Macs

How to Make AI Summaries Stop Dropping the Important Parts: A Copy-Paste Prompt (Tested)

An AI summary fails quietly. It doesn't invent anything, it reads well, every bullet is true — and the one line you needed is simply not there. The exception to the rule. The deadline. The "never do X". Nothing in a clean eight-bullet summary tells you what got cut, so you walk away confident about

dev.toDienstag 18:01 · 13.10.3 Min. Lesezeit
Bild: dev.to

An AI summary fails quietly. It doesn't invent anything, it reads well, every bullet is true — and the one line you needed is simply not there. The exception to the rule. The deadline. The "never do X". Nothing in a clean eight-bullet summary tells you what got cut, so you walk away confident about a document you've only partly read.

That's a different problem from hallucination, and it needs a different fix. You can't fact-check an omission; there's nothing on the page to check. What you can do is make the model show its work: list everything the document contains first, summarize second, then account for every item it left out. Below is that prompt, a side-by-side test against a plain "summarize this", and where it still needs you.

Because "summarize" asks for compression, and compression keeps what's typical of a document, not what's load-bearing in it. The main rules survive. The exceptions to those rules — usually one sentence each, often buried under a heading that sounds minor — are exactly what compression treats as detail.

Three kinds of content go first, and they happen to be the ones that hurt:

Summarize the document below in two passes. Pass 1 — Map: list every section or distinct topic, in order, one line each. Pass 2 — Summary: write the summary (max [N] bullets).

Every bullet must name the section it comes from. Then, Coverage check: list each Pass-1 item that is NOT in the summary, and for each say in one line whether a reader could get hurt by not knowing it (yes/no + why). Numbers, deadlines, exceptions and "must/must not" rules are never dropped silently: include them or list them under Coverage check.

Document: [PASTE] Enter fullscreen mode Exit fullscreen mode The map comes first on purpose. Once the model has written down every section, it can't pretend the small ones don't exist — and the coverage check forces a verdict on each one it skipped. The omission becomes visible, which is the whole point.

I used PEP 8, Python's style guide: long, public domain, full of rules and exceptions to those rules, and easy to check. Two fresh runs (Claude Sonnet, same 8-bullet limit):

Run A was a good summary. Indentation, line length, blank lines, imports, naming, docstrings, comparisons to None, annotations — all correct, all genuinely useful. If you'd never read PEP 8, you'd think you had.

Here's what it didn't mention, checked against the source:

Run B caught all four. The permission-to-deviate section became its first bullet, backwards-compatibility warning included. The 99-character team limit made it into the line-length bullet. And the coverage check listed the sections it still left out, each with a verdict:

Run B also listed a tail of exceptions it had compressed out of the summary: the two narrow cases where a bare except: is acceptable, the warning against return inside finally, the note that name-mangled attributes are still reachable. Not all of that belongs in a summary. All of it is better listed than silently gone.

Same model, same document, same bullet budget. The difference is that Run B had to account for what it cut.

Written with AI assistance. Both summary runs were performed as described and reported faithfully; the claims about what PEP 8 says were checked against the live page at peps.python.org. PEP 8 is public domain — reproduce the test on it or on any document you know well.

This is part of the Verify AI Output series; related: how to stop ChatGPT and Claude from forgetting context in long conversations. I keep prompts like this one — summarization, fact verification, source compilation — in a Notion workspace I actually work from; if you want that library already set up, the AI-Augmented Notion Workspace is free, pay what you want.

If you run your AI work on a system, run the rest on one too. An ATS resume template in English and French, for Word and Google Docs: on Gumroad. A 2027 household budget sheet in French and an invoice and income tracker for micro-entrepreneurs, both on Etsy: YvooLab on Etsy.

Quelle: dev.to (dev.to). Original öffnen