Long Document Analysis
Gemini's 1M-token context window makes it ideal for full-document analysis. Claude handles the structured extraction with high precision. Both produce excellent results with this framework.
I'm providing a {{document_type}} that is approximately {{page_count}} pages long. Analyze the full document and produce: 1. **Executive summary** (under 200 words): The core argument or purpose, key conclusions, and who should read this 2. **Chapter/section breakdown**: For each major section, provide a 2-3 sentence summary 3. **Key data points**: Extract all statistics, figures, dates, and quantifiable claims into a table 4. **Contradictions or gaps**: Note any places where the document contradicts itself or leaves important questions unanswered 5. **Action items**: List every recommendation, next step, or call-to-action mentioned in the document 6. **Critical assessment**: What does this document do well? What does it miss? Rate the strength of evidence on a 1-5 scale If sections are unclear or ambiguous, quote the relevant passage and explain the ambiguity rather than guessing the intent.
Variables to customize
Why this prompt works
Gemini's 1M-token context window makes it ideal for full-document analysis. Claude handles the structured extraction with high precision. Both produce excellent results with this framework.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Get thorough code reviews with actionable feedback tailored to your language, framework, and standards.
Context-Aware Code CompletionProviding the surrounding code and project context lets the model match existing patterns exactly. The constraint against modifying existing code prevents unwanted side effects.
Inline Code SuggestionConstraining suggestions to match existing style and scope produces insertions that feel native to the codebase. The 'no explanation' rule mimics real inline completion behavior.
Code ExplanationThe audience level parameter adjusts complexity automatically. Requiring a usage example ensures the explanation is practical, not just theoretical.