Claude Prompt Templates Checklist: 9 Workflows to Run Today
By the Prompt Shelf team · Updated November 18, 2026 · 7 min read
What it is and why it matters
A claude prompt templates checklist is a short list of reusable prompt patterns, each with the blanks to fill in and the job it handles, so you run the same task the same way every time.
If you use Claude every day, you know the pattern: you write a careful prompt, get a strong answer, and then never see that prompt again. The next week you rebuild it from memory and get a weaker result. A checklist ends that loop. It turns your best prompts into named, repeatable workflows that live in one place.
The timing matters because Claude Projects, ChatGPT custom instructions and Gemini Gems now let you store standing context. When your prompts are written and tested, those features stop being a blank box. You stop paying for the same mistake twice.
Quick answer: A claude prompt templates checklist is a short list of reusable prompts, each with a named role, fill-in blanks, a fixed output format and an uncertainty rule. Build it from the tasks you repeat weekly, test each prompt on real material, and save the winners in Claude Project instructions so you can reuse them in seconds.
The claude prompt templates checklist
Use this table as your pre-flight check. If a prompt is missing two or more rows, it is not ready to save.
| # | Checklist item | What you fill in | Where it belongs |
|---|---|---|---|
| 1 | Role and seniority | "a senior research analyst" | First line of the prompt |
| 2 | Task and deliverable | What the output must be | One sentence after the role |
| 3 | Context | Your role, industry, audience | [BRACKETED] fields |
| 4 | Source material | Files, links, notes | Attached or pasted in |
| 5 | Output format | Table, sections, word count | End of the prompt |
| 6 | Uncertainty rule | "Ask me rather than guess" | One line near the end |
| 7 | Stop condition | "Wait for my choice" | Multi-step prompts only |
| 8 | Style rules | Tone, length, US English | Project instructions |
| 9 | Save step | Where the prompt lives | Project instructions or a notes file |
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 →
Step by step: build and test your own checklist
- List the tasks you repeat each week. Client updates, long report summaries, LinkedIn posts, Google Business Profile replies, MLS listing descriptions and YouTube Shorts scripts all count.
- Pick one task and name the deliverable. "A 150-word client update I can send as-is" is a deliverable. "Help me with clients" is not.
- Write the role and the output format first. A senior role and a fixed format do more work than any amount of enthusiasm.
- Add [BRACKETED] fields for the details that change. Keep the brackets short and specific, like [CLIENT NAME] or [REPORT LENGTH IN PAGES].
- Add an uncertainty rule. Tell the assistant to ask you a question instead of guessing when a field is empty.
- Test it on real material. Run it once with a real document or a real thread, not a made-up example.
- Save the winner in the right place. Claude Projects for recurring client work, custom instructions for tone, a notes file for everything else.
- Repeat with the next task. Six checked prompts beat sixty rough ones.
Copy-paste prompts
Each prompt below is original to this guide. Replace every [BRACKETED] field with your own details. If anything is missing, ask me before you answer.
When to use: you have scattered client updates and need one clean weekly digest.
You are a client success manager writing a weekly digest. Below are my raw notes from [NUMBER] clients this week: [PASTE NOTES].
Task: turn them into one digest for [AUDIENCE, E.G. MY AGENCY PARTNER]. For each client give: what moved, what is blocked, what I need from them. Keep each client to 3 bullet points. End with a 2-sentence "needs attention" list. Use US English, no jargon. If a note is too thin to summarize, write [NEED: WHAT IS MISSING] instead of guessing. If anything above is missing, ask me before you answer.
When to use: a long report or contract and you need the action items, not a book report.
You are a chief of staff. I am attaching [DOCUMENT NAME], about [LENGTH] pages. I am reading it because [YOUR PURPOSE].
Task: give me (1) the bottom line in 3 sentences, (2) every action item with the page or section it appears on, (3) a table of numbers, dates and deadlines, and (4) anything that needs my decision this week. Use only the document. Cite page or section numbers for every point. If a field is missing, ask me before you answer.
When to use: you suspect your prompt library has gaps and duplicates.
You are a prompt librarian auditing my saved prompts. Here is the list: [PASTE PROMPT NAMES OR TEXTS].
Task: group them by job, flag duplicates, and name the jobs I have no prompt for. Give a table with columns: job, prompt I have, quality (good / thin / missing), and one line on the gap. Then list 5 new prompts worth writing first, ranked by how often I repeat the job. If the list is unclear, ask me before you answer.
When to use: several drafts in different voices and you need one consistent style.
You are an editor harmonizing a set of drafts. Here are [NUMBER] pieces I wrote for [PURPOSE]: [PASTE OR ATTACH].
Task: name the 3 style traits that appear in the strongest piece, then edit the others to match. Give line edits in a table: original, suggested, reason. Keep my meaning and my facts. Do not add claims. If two pieces are for different audiences, say so and handle them separately. If anything is missing, ask me before you answer.
Worked example
Before: "Help me with this contract."
After:
You are a contracts specialist explaining terms to a non-lawyer. This is not legal advice. I am attaching [CONTRACT TYPE] between [PARTY A] and [PARTY B]. I am [WHICH PARTY]. For payment terms, term and termination, liability, IP and confidentiality: quote the clause, explain it in plain English, and rate it favorable, neutral or unfavorable to me with a reason. Then list 5 questions for my attorney. If a topic is not covered, say "not covered."
The first version gives the assistant nothing to work with. The second names a role, a document, a party position, five fixed areas and a required format. Same ten seconds of typing, far better answer.
Common mistakes
- Vague role. "You are a helper" produces generic output. Fix: name a senior role and a field, such as "a senior research analyst".
- No output format. The assistant invents one and you reformat it. Fix: ask for a table, sections or a word count every time.
- One prompt doing five jobs. Long mixed prompts get mixed answers. Fix: split them and give each its own checklist row.
- No uncertainty rule. The assistant guesses and you catch it late. Fix: add "ask me rather than guess" and a [NEED:] marker.
- Forgetting to replace the brackets. You paste a prompt and leave [CLIENT NAME] in the send. Fix: search for "[" before you run anything.
- Saving prompts only in chat history. You lose them when the thread rolls off. Fix: paste winners into Claude Project instructions or a notes file.
Frequently asked questions
Do I need a paid Claude plan?
No. Most prompts in this checklist 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.
Will these prompts work in ChatGPT or Gemini?
Yes, most of them will. They are written with Claude features in mind, but 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.
How many prompts should my checklist hold?
Start with the six to nine jobs you repeat every week. A short checklist you actually use beats a long one you open once. Add a prompt only after it has survived a real test on real material.
Where should I store my checklist?
Put tone rules and recurring context in Claude Project instructions, and keep the individual prompts in a notes file you can search. That way a new thread starts fast and your standards travel with you.
Can prompts replace a lawyer, accountant or doctor?
No. Prompts help you understand a document and prepare better questions. Always have important legal, tax, medical and financial decisions reviewed by a qualified professional.
Are the filled-in examples in a pack real client results?
No. The examples show how to fill in each prompt with realistic details. They are not outputs, testimonials or proof of results.
Next step
If you want a full set of tested prompts, start with Claude Power Prompts: 30 Real Work Use Cases with Projects, Files and Long Documents. It covers Projects and instructions, research and synthesis, long documents and file analysis, writing systems, and planning and decision-making. Pick one section, run one prompt on real work this week, and add it to your checklist.