Compare two contract PDFs and find the differences with Gemini
For legal, procurement, and HR teams: upload two PDFs and get an automatic line-by-line list of clause differences.
You are a legal contract analyst. I am uploading two PDF contracts for the same engagement — Version A (old) and Version B (proposed new). Compare them and identify ALL material differences in the following focus areas: {{focus_areas}}.
For each difference found, output in this format:
• [SECTION X.Y / Page N] — Old: "..." → New: "..." — Materiality: [LOW/MEDIUM/HIGH] — Reason: <1-sentence explanation>
Ignore: typo fixes, formatting changes, page numbering, defined-term capitalization (unless meaning changes).
At the end, give a 3-bullet executive summary of the most material changes and what each one means in plain language for the contracting party.Swap the variables inside the [ ] brackets for your own content, then paste into Gemini 2.5 Pro.
See what this prompt actually produces without leaving the site (live AI run, 1 credit).
Gemini's 1M context window plus multimodality make it the only model on the market that can hold two 200-page PDFs at once and cross-reference them (GPT-4 and Claude either blow past their context limits or stumble on OCR accuracy). Legal and procurement teams should make this workflow second nature.
結構化 diff list、每條標 section + page + materiality + 1 句解釋、結尾 executive summary
A description of the intended result. Check this entry's testing notes and try the prompt with your own inputs.
[focus_areas]關注的條款類別（如：payment terms, liability caps, IP assignment, termination clauses, data protection / GDPR）
填下面的欄位，上方 prompt 會即時替換 [方括號] 內容。填好後按「複製組好的 prompt」直接丟進工具。
You are a legal contract analyst. I am uploading two PDF contracts for the same engagement — Version A (old) and Version B (proposed new). Compare them and identify ALL material differences in the following focus areas: {{focus_areas}}.
For each difference found, output in this format:
• [SECTION X.Y / Page N] — Old: "..." → New: "..." — Materiality: [LOW/MEDIUM/HIGH] — Reason: <1-sentence explanation>
Ignore: typo fixes, formatting changes, page numbering, defined-term capitalization (unless meaning changes).
At the end, give a 3-bullet executive summary of the most material changes and what each one means in plain language for the contracting party.Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.
7 Cross-Model A/B-Tested Prompt Techniques (Not Vibes)
Written after six months of A/B testing 200+ prompts on Claude, GPT-4, and Gemini with human raters. Covers persona + constraint stacking, anti-examples, role-reversal QA, cognitive scaffolds, emotional priming, uncertainty CoT, and steelman-first.
5 trust-checking one-liner prompts (no role-play)
After a year of role-play system prompts and 14-step frameworks, here's the takeaway: the thing that actually moved the needle on quality was 5 one-line prompts. No roles, no markdown, no "you are an expert."