Guides

How to Claude Prompts: Write Prompts Claude Follows Every Time

By the Prompt Shelf team · Updated November 17, 2026 · 9 min read

If you searched for how to claude prompts, you probably want more than a list of clever one-liners. This guide is for Claude and ChatGPT power users: freelancers, consultants, managers and operators who use Claude every day and need it to handle real work, not just answer quick questions. You will get one reusable prompt structure, a worked example, and four prompts you can paste today.

Quick answer: Write every Claude prompt in four parts: a role, the task, the context, and the output format. Attach your files or Project knowledge, state what Claude should do when information is missing, and ask for a table or outline you can check. Keep one prompt per recurring task and refine it after each use.

What a Claude prompt is and why structure wins

A Claude prompt is the complete instruction you give Claude before it writes anything back.

Claude follows what you actually write, not what you meant. A one-line request like "help me with this report" forces Claude to guess your role, your goal and your format, and the guess is usually wrong. A structured prompt removes the guessing.

The same structure works in ChatGPT and Gemini. ChatGPT users can paste it into custom instructions or a GPT; Gemini users can paste it into a Gem. Claude adds Projects, which keep your instructions and uploaded files in one place.

Structure beats cleverness. Use five parts, in this order: role, task, context, format, limits. Add a rule for missing information and you have a prompt that survives real work.

Step by step: how to claude prompts that hold up

  1. Name the role and the deliverable. Open with "You are a [role]" and end the opening line with what the output must be, such as a brief, a table or a draft email. Claude performs the role you give it, so make the role specific: "contracts specialist explaining terms to a non-lawyer" beats "assistant."
  2. Attach the evidence. Upload the PDF, spreadsheet or screenshot in the same message, or add it to a Claude Project if you will reuse it. Tell Claude what the file is and what to use it for, because a file with no purpose gets summarized generically.
  3. Set the output format. Ask for a table, an outline or a numbered list, and name the columns or headings. A format you can scan is a format you can check.
  4. Set the limits. State what Claude must not do: no invented numbers, no new facts, no promises you cannot keep. Say which file wins if two files disagree.
  5. Tell Claude what to do when something is missing. Use a line like "If anything is unclear, ask me up to 3 questions before you answer." This single rule prevents more bad output than any other.
  6. Ask for questions before the answer. When the task is complex, tell Claude to stop after the plan and wait for your choice. You keep control of the direction.
  7. Review, then save. Check facts, numbers and legal or financial points before you rely on them. Save the prompt in your Project instructions or a notes file so the next run takes seconds.
Prompt pack for Claude and ChatGPT power users
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

Each prompt below is built on the structure above. Replace every [SQUARE BRACKET] field with your own details, then paste the prompt into Claude, ChatGPT or Gemini.

When to use: you have a long document and need the decision-relevant parts in minutes, not a generic summary.

You are a research analyst. I am attaching [DOCUMENT NAME], about [NUMBER] pages. I need it for [DECISION OR DELIVERABLE] by [DATE].

Task:
1. Give me a 3-sentence bottom line.
2. List the 5 most important points, each with the page or section where it appears.
3. Put every number, date and deadline in a table.
4. List anything that needs action from me or my team.
5. Flag the risks, obligations and unusual terms.

Use only the attached document and cite the page or section for every point. If something is ambiguous, quote it and give both readings. Before you start, ask me up to 3 questions if my purpose or the document type is unclear.

When to use: you must choose between options and want the assumptions exposed, not just a recommendation.

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].

Task:
1. Propose weights for my criteria that add up to 100, with one line explaining each.
2. Score each option 1 to 5 per criterion, with a one-line reason.
3. Show the weighted totals in a table.
4. List the assumptions behind the scores and name which one, if wrong, would change the winner.
5. Say what information would most reduce my uncertainty.

Score anything I gave no evidence for as "unknown," and show how the winner changes if that unknown is high or low. Ask me up to 3 questions before you score if any option is unclear.

When to use: you got a good answer once and want to turn it into a prompt you can reuse every week.

You are an expert at writing reusable AI instructions. Below is an answer I liked and the rough prompt I used: [PASTE THE ANSWER AND THE ORIGINAL PROMPT].

Task: Turn this into one reusable prompt I can paste before similar tasks. Include a role, the task, the context I should fill in, the output format, and rules for what to do when information is missing. Replace every detail that was specific to that one task with a [SQUARE BRACKET] field.

Before you write it, ask me up to 3 questions if anything about how I will reuse this is unclear.

When to use: you need to send a difficult message to a client, manager or vendor without damaging the relationship.

You are a communications coach. I need to send a difficult message to [AUDIENCE, E.G. A CLIENT, MY MANAGER]. Situation: [WHAT HAPPENED]. What I want: [DESIRED OUTCOME]. Hard limits: [WHAT I MUST NOT SAY OR PROMISE]. Tone: [E.G. DIRECT BUT WARM].

Task: Write 2 versions of the message, each under 180 words. Add one line on why each version works. Then list what I have not told you that would change the message, and ask me those questions before you revise. Do not invent facts, deadlines or commitments.

Worked example

Before:

Summarize this report.

That prompt gives Claude nothing to work with. It does not know your role, your purpose or the format you need, so it returns a generic paragraph list that mixes minor points with major ones and cites nothing.

After:

You are a chief of staff preparing a brief for a busy executive. I am attaching a 24-page vendor proposal and I am reading it because I must recommend whether we sign by Friday.

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 my team.
5. Risks and unusual terms.

Use only the document. Cite the page or section for every point. If something is ambiguous, quote it and give both readings. If my goal is unclear, ask me before you write.

The second prompt tells Claude who it is, what you are deciding, when the decision is due and what the output looks like. The result is a brief you can act on: a bottom line, points tied to pages, a table of dates, and a list of risks. The first prompt gives you a summary you have to redo.

Prompt parts at a glance

Part What it does Example starter
Role Sets expertise and point of view "You are a contracts specialist explaining terms to a non-lawyer."
Task States the deliverable "Give me a 3-sentence bottom line and 5 key points."
Context Supplies your facts, files and deadline "I am attaching [DOCUMENT], about [NUMBER] pages, for [DECISION] by [DATE]."
Format Makes the output scannable "Use a table with these columns: ..."
Limits Blocks invented facts and wrong tone "Use only the document. Do not invent numbers."
Missing-info rule Turns guesses into questions "Ask me up to 3 questions before you answer."

Common mistakes

  • One vague sentence. Claude guesses the role, goal and format, and usually guesses wrong. Fix: split the request into role, task, context, format and limits.
  • No files, or files with no purpose. An upload without instructions gets a generic summary. Fix: name the file and say what to use it for.
  • Leaving brackets unfilled. Claude reads [YOUR ROLE] as literal text. Fix: replace every bracket before you paste.
  • No rule for missing information. Claude fills gaps with plausible inventions. Fix: add "ask me rather than guess" and "mark anything unknown as unknown."
  • Expecting a perfect first answer. The first output is a draft, not a verdict. Fix: ask for one revision with a specific change, such as "cut this to 150 words" or "add the page citations."
  • Rewriting the prompt every time. Rebuilding from scratch invites drift. Fix: save the working prompt in your Project instructions or a notes file and reuse it.

Frequently asked questions

Do I need a paid Claude plan?

No. Most prompts in this guide work on the free plan, including the ones that attach a single file. Projects and higher upload limits are paid features, so prompts that rely on them work best with a subscription. Start free and upgrade only when you hit those limits.

Will these prompts work in ChatGPT or Gemini?

Yes. The role, context and format structure works in any modern AI assistant. Where a prompt mentions a Claude Project, use custom instructions or a GPT in ChatGPT, or a Gem in Gemini. Long-document prompts work anywhere you can attach a file, including a PDF or spreadsheet.

How long should a Claude prompt be?

Long enough to carry the role, task, context, format and limits, and not one sentence more. Most prompts for real work run a short paragraph plus a numbered task list. If a sentence does not change the output, delete it. Brevity helps, but a missing detail costs more than an extra line.

What is a Claude Project, and do I need one?

A Project is a shared workspace where your instructions and uploaded files apply to every conversation inside it. You do not need one for the prompts in this guide; pasting the prompt and attaching files works in any chat. Set up a Project when you repeat the same work weekly and want the context to persist.

Are the filled-in examples in a prompt pack real client results?

No. Filled-in examples show how much detail a prompt needs and what a complete answer looks like. They are teaching aids, not outputs, testimonials or proof of results. Treat any example as a model to imitate, not as evidence that a prompt will perform the same way for you.

Can I use these prompts instead of a lawyer or accountant?

No. Prompts that explain contract clauses or compare budgets help you understand a document and prepare better questions. They do not replace professional judgment. Have important legal, tax and financial decisions reviewed by a qualified professional in your state before you act.

Next step

Take one recurring task you do this week, a document brief, a decision or a difficult email, and rebuild its prompt with the six parts above. Run it twice, then save the version that worked in your Claude Project instructions or a notes file.

If you want a full library instead of building each prompt by hand, Claude Power Prompts: 30 Real Work Use Cases with Projects, Files and Long Documents gives you 30 ready-to-use workflows for research, writing systems, document analysis, planning and decision-making, each with a filled-in example. Find the section that matches your task, copy the prompt, replace the bracketed fields and upload your files in the same message.

Get the full pack

More guides

Free prompts.

Two from every pack, as one PDF. Then one email when a new pack is out.

We send one confirmation link first.