🔬 Research
Claude XML Long-Context Memo Skeleton
Build a Claude XML long-context memo skeleton with documents tagged, questions isolated, and no invented citations.
0Reviews
Prompt
Act as a research ops editor for Claude long context. Build an XML-tagged memo skeleton the user can paste above source documents. Do not invent quotes. Do not claim you read files that were not pasted. Inputs: - Memo question: [Question] - Doc list (titles, dates, how they will be pasted): [Docs] - Audience: [Audience] - Must answer / must not answer: [Scope] - Claude feature: [single chat / Project] Generate: 1. Wrapper: <instructions>, <question>, <docs> with <doc id="" title="" date=""> placeholders. Tell the user to paste inside, not to ask me to pretend. 2. Extraction rules: quote with id + locator (page or heading). If not found: NOT IN DOCS. 3. Memo outline: 6 headings. Each heading lists which doc ids should feed it. 4. Conflict rule: if two docs disagree, table them, do not average. 5. Refusal: legal conclusions, medical advice, fake page numbers. 6. Project note: what belongs in a Claude Project vs this paste. Distinct from the existing Claude Project custom instructions prompt; this is a per-memo XML pack. Constraints: - XML must be well-formed in the skeleton. - No fake DOI. - Keep the skeleton short so documents can fill the context window.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Question: What did our 2025 ice test method actually specify, and what did the 2026 wholesale FAQ claim? Docs: (A) Ice method note 2025-11-02, 2 pages, will paste. (B) Wholesale FAQ 2026-04, 1 page, will paste. (C) A blog draft I might paste later. Audience: Ellis (CEO) before a buyer call Must: method temperature, duration, lid state. Must not: a new marketing claim. Feature: single chat, not a Project yet
Example Output
1. Wrapper (paste, then insert docs) <instructions>Answer only from <docs>. Quote with doc id and a heading or short quote. If missing, write NOT IN DOCS. No new ice claims. Audience: CEO pre-call. No legal advice.</instructions> <question>What did the 2025 ice test method specify (temp, duration, lid), and what did the 2026 wholesale FAQ claim?</question> <docs> <doc id="A" title="Ice method note" date="2025-11-02">PASTE</doc> <doc id="B" title="Wholesale FAQ" date="2026-04">PASTE</doc> <doc id="C" title="Blog draft" date="unknown">OPTIONAL PASTE</doc> </docs> 2. Extraction rules Quote: [A, heading]. If a number is not in A or B: NOT IN DOCS. Do not use training-data memory of "typical bottle tests". 3. Outline Method temp / duration / lid (A only). FAQ claims (B only). Diff table A vs B (both). NOT IN DOCS list. What we may say on the buyer call (only overlapping facts). Appendix: C if pasted, else ignore. 4. Conflicts If A says 72 F / 24h / lid closed and B says 48h, table it. Do not average to 36h. 5. Refusal No lawyer memo. No fake page 3 if the paste is 2 pages. 6. Project vs paste This XML is per call. A Claude Project would hold A+B standing; that is a different prompt. Single chat: paste A and B under the tags now.