How to Use Claude Prompts for Research, Documents and Decisions
By the Prompt Shelf team · Updated November 19, 2026 · 9 min read
How to use Claude prompts: what it is and why it matters
A Claude prompt is the full instruction you send Claude before it answers: your role, goal, context, output format, and limits in one message. How to use Claude prompts well is the difference between a chat that ends in a shrug and a workflow you repeat every week.
This guide is for Claude and ChatGPT power users who already talk to AI daily but want repeatable results on real work. It fits freelancers, consultants, managers, and operators who read long reports, contracts, and spreadsheets and need clear summaries and comparisons. It also fits anyone who created a Claude Project and is unsure what to put in the instructions or knowledge files.
Claude handles long context and careful reading better when the brief is specific. A vague prompt gets a vague answer, no matter which model you use. A prompt with a role, a task, a format, and a stop condition gets output you can use the same day.
Quick answer: Use Claude prompts by giving a role, a task, context, a format, and a limit in one message. Set up a Claude Project with instructions and knowledge files for recurring work. Copy a prompt, fill the [BRACKETED] fields, upload your files, answer Claude's questions, then check facts, numbers, and legal or financial points before you rely on the result.
Step by step: from blank chat to a repeatable workflow
- Pick one recurring task. Choose work you do at least monthly, such as a weekly report, a client proposal, or a document summary. A prompt that serves one real task beats ten clever one-offs.
- Write the role, task, context, format, and limit. Use this skeleton: "You are [ROLE]. I need [TASK]. Context: [DETAILS]. Format: [STRUCTURE]. Do not [LIMIT]."
- Fill the context with specifics. Add the audience, the goal, the deadline, and the files involved. The more concrete the context, the less Claude has to guess.
- Set a stop condition. Tell Claude when to stop and what to ask. For example: "If anything is missing, ask me up to 3 questions before you write."
- Store the prompt in a Claude Project. Put the prompt and your style rules in the Project instructions, and upload your reusable files to the Project knowledge.
- Test it with real files. Upload a PDF, spreadsheet, or screenshot and run the prompt once. Read the output for missing facts and wrong tone.
- Tighten the weak spots. Add the rule Claude broke to your instructions, shorten any step it skips, and save the improved version.
- Reuse and refresh. Run the same prompt each week. Update the instructions when your business, offer, or audience changes.
Claude Power Prompts: 30 Real Work Use Cases with Projects, Files and Long Documents
Ready-to-use Claude workflows for research, writing systems, document analysis, planning and decision-making, each with a filled-in example.
$19 · See what's inside →
Copy-paste prompts you can run today
Each prompt uses [BRACKETED] fields. Replace every bracket with your own details before you send it. If a bracket has no obvious answer, ask Claude a question instead of guessing.
When to use: You have a long report, proposal, or contract and need a short brief before a meeting.
You are a chief of staff preparing a brief for a busy executive. I am attaching [DOCUMENT NAME], about [LENGTH] pages. I am reading it because [YOUR PURPOSE].
Task:
1. Bottom line in 3 sentences.
2. The 7 most important points, each with the page or section where it appears.
3. Numbers, dates, and deadlines in a table.
4. Anything that requires action from me or my team.
5. Risks, obligations, or unusual terms.
6. Questions I should ask the author.
Use only the document. Cite page or section numbers for every point. If something is ambiguous, quote it and explain both readings. If any part of my request is unclear, ask me up to 3 questions before you start.
When to use: You have several sources on one topic and need to see where they agree and disagree.
You are a research analyst. I am providing [NUMBER] sources about [TOPIC]: [LIST OR ATTACH SOURCES].
Task:
1. Build a table with one row per source: title, author or publisher, date, main claim, evidence type, and a reliability note.
2. List where the sources agree.
3. List where they disagree, quoting each side and naming the source.
4. Give a synthesis of 150 to 200 words that answers: [YOUR SPECIFIC QUESTION].
5. List what none of the sources answer.
Use only the sources I provided. Attribute every claim to a source. If a source is missing a date or author, say so rather than guessing. Ask me up to 3 questions if the topic or question is unclear.
When to use: You are choosing between two or more options and want the reasoning visible.
You are a decision analyst. I must choose between [OPTION A], [OPTION B], and [OPTION C]. Context: [SITUATION AND GOAL]. What matters most to me: [CRITERIA]. Constraints: [BUDGET, TIMING, OTHER LIMITS]. Facts I have about each option: [FACTS].
Task:
1. Propose weights for my criteria that add to 100, with a one-line reason for each.
2. Score each option 1 to 5 per criterion, with a one-line reason based on my facts.
3. Show the weighted totals in a table.
4. List the assumptions behind the scores and which one, if wrong, would change the winner.
5. Name the information that would most reduce my uncertainty.
Do not invent facts about the options. Score "unknown" where I gave no information, and show how the result changes if it is high or low. Ask me up to 3 questions if an option or criterion is unclear.
When to use: You created a Claude Project and need the text for the instructions field.
You are an expert at configuring AI assistants for professional work. I am setting up a Claude Project and need the text for its "Project instructions" field.
About me and this project:
- My role: [YOUR ROLE AND INDUSTRY]
- What this Project is for: [THE RECURRING WORK, E.G. CLIENT PROPOSALS, WEEKLY REPORTS]
- Who reads the output: [AUDIENCE]
- Tone and style rules: [TONE, E.G. DIRECT, NO JARGON, US ENGLISH]
- Things the assistant must never do: [HARD RULES, E.G. NEVER INVENT NUMBERS]
- Files I will upload to the Project knowledge: [LIST OF FILES]
Task: Write Project instructions of 250 to 400 words. Structure them as: (1) who I am and what I do, (2) the goal of this Project, (3) how to use the uploaded files, including which file wins if they conflict, (4) default output format, (5) style rules, (6) rules for uncertainty: ask me a question rather than guess, and flag any statement not supported by my files.
Before writing, ask me up to 3 questions if anything above is missing or vague. Then give the final instructions in one block I can paste directly.
Worked example: a market scan brief
Maya runs a one-person consulting practice. She has a 40-page market scan and a partner meeting on Friday. She needs to decide whether to enter the Austin market.
Before:
Summarize this report.
Claude returns a generic recap of ten bullets with no page references, no dates, and no questions. Maya still has to read the full document to find what matters for her decision.
After:
You are a chief of staff preparing a brief for a busy executive. I am attaching a 40-page market scan about the Austin consulting market. I am reading it because I must decide by Friday whether to enter that market.
Task:
1. Bottom line in 3 sentences.
2. The 7 most important points, each with the page or section where it appears.
3. Numbers, dates, and deadlines in a table.
4. Anything that requires action from me or my team.
5. Risks, obligations, or unusual terms.
6. Questions I should ask the author.
Use only the document. Cite page or section numbers for every point. If something is ambiguous, quote it and explain both readings.
Claude returns a 3-sentence bottom line, 7 points with page numbers, a table of dates, and 5 questions Maya can ask the author. The difference is not the model. The difference is the brief.
| Part of the prompt | Before | After |
|---|---|---|
| Role | "You are Claude" | "You are a chief of staff preparing a brief" |
| Task | "Summarize this report" | "Give a bottom line in 3 sentences, then 7 points with page numbers" |
| Context | None | "40-page market scan; I am deciding whether to enter the Austin market" |
| Format | None | "Numbered points, a table for dates, a question list" |
| Limit | None | "Use only the document; cite page numbers; quote ambiguous lines" |
Common mistakes and how to fix them
- Asking for everything at once. Long, multi-goal prompts produce shallow output. Fix: split the work. Run one prompt for the summary, another for the risks, and a third for the questions to ask.
- Skipping the role. "Summarize this" gives a generic tone. Fix: open with "You are [ROLE]" so Claude matches the audience and vocabulary.
- Leaving out the format. Claude defaults to what it guesses. Fix: name the output shape, such as "a table," "a 150-word paragraph," or "a numbered list of 7."
- Uploading files without saying how to use them. Fix: state which file wins if two conflict, and tell Claude to cite the page or section for every point.
- Accepting the first answer as final. Claude will guess when context is thin. Fix: ask it to flag anything not supported by your files, and check facts, numbers, and legal or financial points yourself.
- Writing prompts you cannot reuse. Fix: save the prompt in your Project instructions or a notes file, with the [BRACKETS] intact, so you can copy it again in seconds.
Frequently asked questions
Do I need a paid Claude plan?
No. Most prompts work on the free plan. Prompts that use Projects or several large file uploads work best on a paid plan, because Projects and higher upload limits are part of paid plans. Start free, then upgrade only if you hit a limit.
Will these prompts work in ChatGPT or Gemini?
Yes, most of them will. The role, context, and format structure works in any modern AI assistant. Where a prompt mentions Projects, use custom instructions or a GPT in ChatGPT, or a Gem in Gemini. Adjust file limits to what your plan allows.
Are the filled-in examples real client results?
No. The examples show how to fill in each prompt with realistic details so you can see the level of detail that works. They are not outputs, testimonials, or proof of results. Treat each one as a formatting model, not as evidence that a real client task succeeded.
Can I use these prompts instead of a lawyer or accountant?
No. Prompts for contracts and budgets help you read a document, spot unusual terms, and prepare better questions for an expert. They do not replace professional judgment. Have important legal, tax, and financial decisions reviewed by a qualified professional before you sign or spend.
How long should a prompt be?
Long enough to carry the role, task, context, format, and limit. Most strong prompts run 80 to 250 words. Shorter is fine for simple tasks. Longer helps when you attach files, set style rules, or need a specific structure back.
What is a Claude Project, and why use one?
A Claude Project is a workspace where you store instructions and knowledge files that apply to every chat inside it. Use one for recurring work, such as weekly reports or client proposals. Put your style rules and reusable files there so you do not paste them again each time.
Related guides
- Claude Prompt Templates Checklist: 9 Workflows to Run Today
- Claude Projects Prompts Examples for Your Daily Work
Next step
If you want these prompts ready to run, pick up Claude Power Prompts: 30 Real Work Use Cases with Projects, Files and Long Documents. It has 30 filled-in prompts across setup, research, long documents, writing systems, and decisions. Find the section that matches your task, copy the prompt, replace the [BRACKETS], and upload your files in the same message.