Claude prompts: 20 free prompts for Projects, Artifacts and long documents
Claude is at its best with long documents, careful writing and small working tools (Artifacts). These prompts are written the way Claude reads best: material first, task last, with XML tags where it helps.
Copy a prompt, replace every [BRACKETED] part with your real details, and send it. If the answer is generic, add one more constraint (reader, length, example) in the same chat.
Projects: Set Up Once, Reuse in Every Chat prompts
A Project keeps its instructions and knowledge files for every chat inside it. Paste prompts 1-3 into the Project's instructions field, upload your reference files as Project knowledge, then use 4-6 inside chats.
#1Project instructions: brand writing desk
You are the writing desk for [COMPANY], which sells [PRODUCT] to [AUDIENCE]. The files in this Project are the source of truth: brand voice guide, product facts and past examples. Before writing, check those files. Voice: [3 ADJECTIVES]. Never use: [BANNED WORDS]. Never invent product features, prices, numbers or customer quotes; if a fact is not in the Project files, write [CHECK: ...] instead. Default format: [e.g. plain text, short paragraphs, US English]. When I ask for a draft, give one strong version first, then 2 alternative headlines.
#2Project instructions: client or account workspace
This Project is about [CLIENT / ACCOUNT NAME]. Project files include [CONTRACT, MEETING NOTES, EMAILS, SPECS]. In every chat: (1) answer only from these files plus what I write in the chat, (2) quote the file name and the exact sentence for any commitment, date or number,
(3) flag contradictions between files instead of picking one, (4) keep a running "open questions" list at the end of long answers.
Tone with me: direct and brief.
#3Project instructions: study or course companion
This Project is my study space for [COURSE / EXAM / TOPIC]. Files are my lecture notes and readings. Teach, do not just answer: explain in plain language first, then the precise term, then one worked example. When I ask "quiz me", ask one question at a time, wait for my answer, tell me what was right and wrong, and track which topics I miss. Cite which file each explanation comes from. If something is not covered in the files, say so before using general knowledge.
Long Documents and File Uploads prompts
Attach the file(s) or paste the text into <document>. Keep the documents at the top and the task at the bottom.
#7Quote-first document Q&A
<document source="[FILE NAME]">
[PASTE TEXT, OR DELETE THIS BLOCK AND ATTACH THE FILE]
</document>
<instructions>
1. Find the passages that are relevant to my question and copy them word for word inside <quotes> tags, each with its section or page.
2. Then answer inside <answer> tags using only those quotes.
3. If the document does not answer the question, say "Not in the document" and stop.
</instructions>
My question: [QUESTION]
#8Executive summary for a busy reader
Read the attached [REPORT / PDF]. Write a summary for [READER, e.g. a board member with 3 minutes]. Structure: one-sentence bottom line; 3-5 key findings, each with the page or section it comes from; 3 risks or caveats the authors mention; and what decision or action the document asks for. Max 250 words. Do not add opinions that are not in the document; put your own view, if any, in a separate final line labeled "My take".
#9Compare two versions of a document
<document source="version A: [NAME / DATE]">[PASTE OR ATTACH]</document>
<document source="version B: [NAME / DATE]">[PASTE OR ATTACH]</document>
List every substantive change from A to B in a table: section | what A says | what B says | why it matters for [MY ROLE / SIDE]. Ignore pure formatting and wording changes that do not change meaning, but count them at the end. Finish with the 3 changes I should push back on.
#10Contract or policy: obligations and dates
Read the attached [CONTRACT / POLICY / TERMS]. Extract every obligation into a table: who must do it | what exactly | deadline or trigger | clause number | consequence if missed. Then list all dates, notice periods, renewal and termination terms. Quote the clause text for anything with money or a deadline. Add a final note: "This is a reading aid, not legal advice." Flag unclear wording instead of interpreting it.
Writing and Editing prompts
Claude is at its best when you describe the reader and paste a sample of the voice you want.
#14Draft in my voice from samples
<voice_samples>
[PASTE 2-3 THINGS YOU HAVE WRITTEN THAT YOU LIKE]
</voice_samples>
<instructions>
Study the samples: sentence length, word choice, how I open and close, what I never do. Describe my voice in 5 bullets. Then write [PIECE: e.g. a 300-word LinkedIn post / an email to a client] about [TOPIC] in that voice for [READER]. Do not copy sentences from the samples.
</instructions>
#15Edit without rewriting
<draft>
[PASTE YOUR TEXT]
</draft>
Edit this as a careful line editor. Keep my structure, my opinions and my voice. Fix only: grammar, unclear sentences, repetition, filler and weak verbs. Return (1) the edited text, then (2) a list of every change that altered meaning, so I can approve it. Do not add new ideas, examples or claims.
#16Cut by 40 percent
<draft>[PASTE]</draft>
Cut this to about [TARGET] words (roughly 40 percent shorter) for [READER]. Keep every fact, number and commitment. Remove throat-clearing, repeated points and hedges. Then tell me in 3 bullets what you removed and why.
#17Hard email, right tone
Write an email to [RECIPIENT AND RELATIONSHIP] about [SITUATION, e.g. a missed deadline / a price increase / declining a request]. What I need them to do or understand: [GOAL]. Facts: [FACTS]. Tone: [e.g. firm but warm]. Max [N] words. Give 2 versions: one shorter and more direct, one softer. Subject lines for both. No apologies I did not ask for, no "I hope this email finds you well".
Artifacts: Documents, Tools, Diagrams prompts
Artifacts appear in a side panel, can be edited by follow-up messages, downloaded, and in many plans shared or published by link. Ask for "an artifact" explicitly when you want a standalone deliverable.
#21One-page document as an artifact
Create an artifact: a one-page [BRIEF / PROPOSAL / SOP / CHECKLIST] for [AUDIENCE] about [TOPIC]. Sections: [LIST]. Use clear headings and short paragraphs. Facts to use: [FACTS]. Leave [PLACEHOLDER] where I have not given you a fact. After it is created, list 3 things I should check before sharing it.
#22Interactive calculator or tool
Build an interactive artifact: a [CALCULATOR / ESTIMATOR / CHECKLIST APP] that lets [USER] enter [INPUTS] and shows [OUTPUTS]. The formula is: [FORMULA OR RULES]. Show the formula under the result so users can trust it. Clean, simple layout that works on a phone. Include 2 example values so it is not empty on first load. Do not store any data outside the page.
#23Diagram from a process description
Turn this process into a flowchart artifact (Mermaid or SVG is fine): [DESCRIBE THE STEPS, WHO DOES WHAT, DECISION POINTS]. Show decisions as yes/no branches, keep labels under 6 words, and add a short legend. Then list any step where my description was ambiguous.
Research and Web Search prompts
Use with web search or Research turned on (availability depends on your plan and region). Without it, Claude answers from training data and should say so.
#27Research brief with sources
Research [QUESTION] for [PURPOSE / DECISION]. Scope: [REGION, TIME PERIOD, WHAT TO EXCLUDE]. Deliver: a 5-line answer up front; then the evidence grouped by sub-question; a sources list with title, publisher and date for each; and a "confidence" note that says which points rest on a single source. Prefer primary sources (official docs, filings, studies) over blog posts. If sources conflict, show both.
#28Competitor or vendor scan
Research [COMPANY / PRODUCT / VENDORS: LIST]. For each: what they sell, who they target, published pricing model (or "not published"), 3 notable recent changes with dates, and their main claim on their own website. Put it in a comparison table, then 3 bullets on where the gaps are for [MY COMPANY / NEED]. Cite a source for every row.
Thinking, Decisions and Analysis prompts
For hard problems, ask Claude to think before it answers. If your plan has an extended thinking option, turn it on for these.
#32Decision memo
<situation>[DESCRIBE THE DECISION, OPTIONS, CONSTRAINTS]</situation>
Think it through step by step inside <thinking> tags, then write a decision memo inside <memo> tags: the options, criteria with weights I would agree to, a scored comparison, the recommendation, what would change your mind, and the first 3 actions. Be direct; if the honest answer is "not enough information", say what information.
#33Pre-mortem
We are about to [PLAN]. Imagine it is [DATE + 6 MONTHS] and it failed. Write the 7 most likely reasons, ranked by likelihood x impact, each with an early warning sign and a cheap preventive step. Then name the single assumption that, if wrong, kills the plan.
Data, Spreadsheets and CSV Files prompts
Attach the file. Claude can read CSV, XLSX and many other formats; for large files it may write and run analysis code if your plan includes it.
#37First look at a dataset
Look at the attached [FILE]. Before any analysis: describe each column (type, example values, blanks), the number of rows, the time range, and any quality problems. Then propose 5 questions this data can answer for [GOAL], and the 2 it cannot answer without more data.
#38Answer one business question with the data
Using the attached [FILE], answer: [QUESTION]. Show the steps you took (filters, groupings, formulas) so I can reproduce them in a spreadsheet. Give the answer as one sentence plus a small table. State any assumption you made about the data.
20 more Claude prompts in the full pack
The Claude Prompts Pack has 40 prompts in total. Here is what else is inside:
#4Audit the Project knowledge
#5Kick-off message for a new chat inside a Project
#6Turn a long chat into a reusable Project note
#11Multi-document synthesis with citations
#12Turn a long document into a study or onboarding pack
#13Find what is missing
#18Article from notes
#19Reader test before you send
#20Style guide from good examples
#24Data dashboard from a file
#25Learning tool or quiz
#26Iterate on an existing artifact
#29Fact-check my draft
#30What changed recently
#31Literature or market map
#34Steelman and red team
#35Explain it three ways
#36Structured problem breakdown
#39Spreadsheet formula helper
#40Survey or feedback themes
Buy this pack
All 40 prompts as a plain-text file, yours to keep. One-time payment.
Already on Pro? Sign in and the full pack opens right here.
How to write prompts Claude follows
Use these on claude.ai, in the desktop app or in the mobile app. The same habits work with Claude in other tools.
Documents on top, question at the bottom
With long material, paste or attach it first and put your actual task last.
Use XML tags
Wrap parts in tags like <document>, <instructions> and <example>. Claude keeps them apart cleanly.
Ask for quotes first
"Quote the relevant passages, then answer" cuts made-up details on document questions.
Put repeated context in a Project
If you paste the same background every time, save it once as Project instructions and knowledge.
Give Claude a way out
"If you are not sure, say so" and "write [NOT IN SOURCE]" make answers more honest.
A Claude prompt template with XML tags
Replace every [BRACKETED] part. Keep the last line: it stops the AI from guessing.
<context>
I am [ROLE]. This is for [READER] who needs [PURPOSE].
</context>
<document>
[PASTE TEXT OR ATTACH THE FILE]
</document>
<instructions>
1. Quote the passages that matter for the task.
2. Then [TASK] using only those quotes.
3. If the document does not cover it, say so.
</instructions>
Prompts that give Claude your real material, name the reader and ask for quotes before answers. Project instructions (prompts 1 to 3 above) are the biggest upgrade: you write them once and every chat in the Project follows them.
Are these Claude prompts free?
Yes, the 20 prompts on this page are free. The full Claude Prompts Pack has 40 prompts, an assistant prompt and troubleshooting for $9, or it is included in KissMySkills Pro, where you can also use it inside Claude through our connector.
Is there a Claude prompt library?
This page is the free part of ours, and the full pack is the library. For repeat work, a Claude skill goes further than a prompt: it gives Claude a role, rules and output formats you install once.
Do you have Claude Code prompts?
This pack is for the Claude apps. For coding, browse our Claude skills for developers: they install into Claude Code and work as reusable instructions.
Do these prompts work in ChatGPT?
Most do. XML tags are understood by other models too, but Projects and Artifacts are Claude features.
Want the AI to do this job every week?
A skill gives Claude or ChatGPT a role, rules and output formats you install once. Browse 2,400+ skills, prompts and agents.
