Chunking: Why Split Size Matters
Documents are split into chunks before embedding.
The prompt
Split this document into retrieval-ready chunks. Rules: each chunk 200-400 words, never split mid-paragraph, prepend each chunk with a 1-line context header stating the document title and section it came from. Return as a numbered list. [paste document]
What to replace
Swap these placeholders for your own details before running the prompt:
[paste document]your own value
Pro tip: Prepending a short context header to every chunk ("From: 2025 Pricing Policy > Refunds") dramatically improves retrieval accuracy for ambiguous queries.
How to use this prompt
- Copy the prompt using the button above.
- Replace [paste document] with your own details — the more specific you are, the better the output.
- Paste it into ChatGPT and run it.
- If the answer feels generic, add constraints: audience, length, tone, and what to avoid. That single change fixes most weak output.
Learn the technique
Chunking: Why Split Size Matters
Module 1 — RAG Fundamentals · RAG & Custom AI Knowledge
Related prompts
What RAG Actually Does
RAG (Retrieval-Augmented Generation) retrieves the most relevant passages from your documents and injects them into the prompt before the model answers.
ChatGPT / ClaudeCustom GPTs & Claude Projects
Both ChatGPT (Custom GPTs) and Claude (Projects) let you upload documents and set standing instructions — a no-code RAG setup.
ClaudeWriting Docs That Retrieve Well
Retrieval quality starts with document quality.
ChatGPTSQL Query Explainer
Understanding or debugging unfamiliar queries. Ideal when you inherit a legacy codebase, review a teammate's pull request, or hit a slow query you did not write. Asking for a plain-English walkthrough before the optimisation notes means you understand the intent first, so you can tell a genuine bug from a deliberate design decision.
ClaudeCode Review Pass
Pre-review pass before submitting a pull request
ChatGPTBlog Post Outline Generator
Planning long-form content before writing