Most people using Claude Projects are leaving 80% of its power on the table. They open a project, paste some context, ask a question, and close it — treating it like a slightly fancier chat window. I did the same thing for the first two months. Then I spent a serious chunk of time in 2026 rebuilding my entire client workflow around Claude Projects’ persistent memory system, and the difference was night and day. Response quality went up. Setup time per client dropped from 45 minutes to under 10. And I stopped repeating myself in every single conversation.
According to McKinsey’s 2023 report, generative AI could add $2.6–$4.4 trillion annually to global productivity.
This prompt swipe file is the result of that rebuild. Every prompt below is copy-paste ready, tested in real work, and organized by workflow stage. Whether you’re a freelancer managing multiple clients, a solopreneur running content operations, or a consultant who needs Claude to “know” your methodology without re-explaining it every session — this guide will change how you use Projects.
Why Claude Projects Persistent Memory Actually Works (And Why Most People Set It Up Wrong)
Claude Projects gives you a persistent context window — essentially a “brain” that stays loaded across every conversation inside that project. You can store up to roughly 200,000 tokens of project instructions and uploaded documents. That’s around 150,000 words of permanent context Claude reads before you even type your first message.
The mistake I see constantly: people write one vague paragraph in the Project Instructions box and call it done. Something like “You are a helpful assistant for my marketing business.” That’s not persistent memory — that’s a system prompt. Real persistent memory means engineering your Project Instructions and document uploads so that Claude has everything it needs to act like a specialist who has been working with you for years.
Here’s what a well-structured Claude Project actually contains:
- Project Instructions: Your role definition, output rules, tone guidelines, and non-negotiables
- Uploaded documents: SOPs, client briefs, brand voice guides, past examples, competitor research
- Conversation history: Claude retains context within a single conversation, not across conversations — which is why your Project Instructions need to carry the load
The prompts in this swipe file are designed to work within that architecture. Some go in your Project Instructions. Some are conversation starters. Some are mid-workflow prompts you’ll use repeatedly. I’ve organized them into six sections based on how I actually use Projects day-to-day.
Section 1: Project Instructions — Foundation Prompts to Set Up Any Project
These prompts go directly into the Project Instructions field. Think of them as the “always-on” layer of your persistent memory. Get these right and every conversation in that project starts with Claude already calibrated.
Prompt 1: The Role + Rules Foundation Block
When to use it: At the start of any new project. This is your baseline. Paste this into Project Instructions, then customize the bracketed sections.
You are [Role Title] working exclusively for [Your Name / Business Name].
YOUR PRIMARY JOB: [One-sentence description of what this project is for — e.g., "Help me produce client-ready blog content for B2B SaaS companies."]
RULES YOU MUST FOLLOW IN EVERY RESPONSE:
- Never use filler phrases like "certainly!", "great question!", or "of course!"
- Always write in [American / British] English
- Default output format: [bullets / prose / numbered list] unless I specify otherwise
- When I ask for drafts, always produce the full draft — never truncate or summarize
- If you're uncertain about something, say so directly instead of guessing
MY BACKGROUND: [2-3 sentences about your experience, niche, and who your audience is]
THINGS I HATE IN OUTPUT: [List 3-5 specific things — e.g., "Passive voice overuse", "Starting sentences with 'This'", "Vague CTAs like 'learn more'"]Prompt 2: The Client Context Block
When to use it: Create one Project per client. This block gives Claude everything it needs to know about that specific client without you repeating it every session.
CLIENT PROFILE — [Client Name]
Industry: [e.g., B2B HR Software]
Company size: [e.g., 12-person startup, Series A]
Target audience: [e.g., HR managers at companies with 50-500 employees]
Main product/service: [1-2 sentences]
Key differentiator: [What makes them different from competitors]
Competitors to be aware of: [List 3-5 competitors by name]
Tone of voice: [e.g., "Confident but approachable — think smart friend, not consultant"]
Topics they DO NOT want to cover: [e.g., "Avoid any references to layoffs or RIFs"]
Current main goals: [e.g., "Drive demo signups through thought leadership content"]
APPROVED TERMINOLOGY:
- Use "[X]" instead of "[Y]" — e.g., "people ops" not "HR"
- Their product is always called "[Product Name]", never "[alternative name]"Prompt 3: The Output Standards Block
When to use it: Add this to any project where you’re producing deliverables — content, reports, emails, proposals. It trains Claude on your quality bar so you stop editing the same things every time.
OUTPUT QUALITY STANDARDS FOR THIS PROJECT:
WRITING STYLE:
- Sentence variety: mix short punchy sentences with longer explanatory ones
- Reading level target: [Grade 8-10 / Grade 12 / Professional]
- Avoid starting three consecutive sentences with the same word
- Every paragraph must have a clear job — if a paragraph doesn't move the reader forward, cut it
STRUCTURE DEFAULTS:
- Blog posts: Hook → Context → Main points (H2/H3) → Practical takeaway → CTA
- Emails: Subject line → One-sentence hook → Body (max 3 paragraphs) → Single clear CTA
- Reports: Executive summary (3 bullets) → Findings → Recommendations → Next steps
FORMATTING:
- Use headers for anything over 400 words
- Bold the most important phrase in each section — only one per section
- No bullet lists with more than 7 items. If it goes over 7, group them into sub-categoriesSection 2: Starting New Conversations Inside a Project
Even with perfect Project Instructions, how you open a conversation matters. These prompts are conversation starters designed to activate Claude’s full context immediately and get useful output in the first exchange.
Prompt 4: The Session Kickoff with Deliverable Spec
When to use it: Start of any working session where you need a specific output. Much more effective than just “write me a blog post about X.”
Starting a new work session. Today I need to produce:
DELIVERABLE: [e.g., One 1,500-word blog post]
TOPIC: [Specific topic, not a category]
ANGLE: [The specific take or argument — e.g., "Why most onboarding checklists fail remote employees"]
TARGET READER: [Be specific — e.g., "A first-time people ops manager at a 75-person startup"]
Key point I want the reader to walk away with: [One sentence]
Any specific stats, examples, or sources to include: [List them or say "none"]
Deadline context: [e.g., "This goes to client for review tomorrow"]
Confirm you have everything you need, or ask me one clarifying question before you start.Prompt 5: The “Resume Previous Work” Opener
When to use it: When you’re continuing a multi-day project and want Claude to orient itself quickly before you dive in. Paste the relevant section of previous work directly into this prompt.
Resuming work on [project/deliverable name]. Here's where we left off:
[Paste the last version of the document, outline, or draft here]
STATUS: [e.g., "Outline approved, need to write sections 2 and 3"]
FEEDBACK RECEIVED: [Any client or internal feedback since last session — or "none yet"]
TODAY'S GOAL: [Exactly what you want to accomplish in this session]
Read through what I've pasted, then tell me in one sentence what you understand today's goal to be before starting.Prompt 6: The Constraint-First Opener
When to use it: When you have very specific constraints (word count, platform, audience restrictions) that override your usual defaults. This prevents Claude from defaulting to your standard format when the situation calls for something different.
OVERRIDE FOR THIS CONVERSATION ONLY:
Ignore your default output format for this session. Here are the specific constraints:
Platform: [e.g., LinkedIn, internal Slack post, regulatory submission]
Hard word limit: [X words — this is a hard ceiling, not a suggestion]
Restricted language: [e.g., "No superlatives. No statistics unless I provide them. No future tense."]
Specific structure required: [e.g., "Must follow AIDA: Attention, Interest, Desire, Action"]
Task: [Your actual request]
After you produce the output, tell me the word count.Section 3: Content Production Prompts for Solopreneurs and Freelancers
These are the prompts I use most frequently in my day-to-day content work. They’re designed for speed — getting high-quality first drafts without a ton of back-and-forth.
Prompt 7: The Deep-Angle Blog Post Brief
When to use it: When you need a blog post that actually takes a position instead of just summarizing information. The angle specification is what separates useful drafts from generic ones.
Write a [word count] blog post on the following brief:
TITLE DIRECTION: [Not the final title — the direction, e.g., "Something that signals this is for experienced practitioners, not beginners"]
CORE ARGUMENT: [The specific claim the post makes — e.g., "Employee engagement surveys are making the problem worse, not better"]
EVIDENCE TO USE: [Specific stats, examples, studies, or "draw from general knowledge but flag anything I should verify"]
SECTIONS TO HIT:
1. [Section 1 description]
2. [Section 2 description]
3. [Section 3 description]
THINGS TO AVOID: [Common angles, clichés, or approaches that are overused in this space]
CLOSING ACTION: [What the reader should do, think, or feel after reading]
Write the full post. Do not summarize or skip sections.Prompt 8: The Email Sequence Builder
When to use it: When a client needs a nurture or onboarding email sequence. This produces all emails in one pass with logical flow between them.
Write a [X]-email sequence for [purpose — e.g., "new subscriber onboarding for a SaaS productivity tool"].
SEQUENCE GOAL: [What should the reader do or believe by the end of the sequence?]
SENDER PERSONA: [Who is writing these — e.g., "The founder, casual and direct"]
READER'S STARTING STATE: [What do they know/feel when they join? e.g., "They just signed up for a free trial, they're curious but haven't opened the app yet"]
For each email, provide:
- Subject line (+ one A/B variant)
- Preview text (max 90 characters)
- Full email body
- CTA
EMAIL SCHEDULE:
Email 1: [Timing and goal — e.g., "Send immediately. Goal: get them to complete profile setup"]
Email 2: [e.g., "Day 2. Goal: show one quick win they can get in 10 minutes"]
Email 3: [e.g., "Day 5. Goal: address the most common objection to upgrading"]
Maintain consistent voice across all emails. Flag any place where you've made an assumption I should verify.Prompt 9: The Social Proof Asset Pack
When to use it: After a client interview or case study session. Paste in the raw transcript and get multiple assets from one pass.
I'm going to paste in a raw client interview transcript. From it, produce the following assets:
1. Case study (600 words) — structure: Challenge → Approach → Results → Quote
2. Three pull quotes suitable for a sales deck (each under 50 words)
3. One LinkedIn post (200-250 words) written from the client's perspective
4. Five short testimonial snippets (1-2 sentences each) for a website
Rules:
- Only use information from the transcript — do not invent details, stats, or results
- If the transcript doesn't have a specific result or metric, write [METRIC NEEDED] as a placeholder
- Keep the client's natural voice in the LinkedIn post
- Flag any quote you've cleaned up or paraphrased
TRANSCRIPT:
[Paste transcript here]Prompt 10: The Content Repurposing Engine
When to use it: When you have a long-form piece (blog post, podcast transcript, webinar notes) and need to get multiple formats out of it efficiently.
I'm pasting in a piece of long-form content. Repurpose it into the following formats:
1. Twitter/X thread (8-10 tweets, each under 280 characters, first tweet is a hook)
2. LinkedIn carousel outline (8 slides — give a title and 2-3 bullet points per slide)
3. Newsletter intro paragraph (150 words max — written as if introducing this topic to your list)
4. One-paragraph executive summary for internal use
Rules:
- Preserve the original argument and key points — don't soften or change the position
- The Twitter thread should feel like a real person wrote it, not a robot
- Do not start any tweet with "Did you know" or "Here's why"
ORIGINAL CONTENT:
[Paste content here]Section 4: Strategy and Research Prompts for Consultants
These prompts treat Claude as a thinking partner and research assistant. They’re most powerful when you’ve uploaded reference documents (competitor reports, market data, client briefs) to your Project.
Prompt 11: The Competitor Gap Analysis
When to use it: When you need to help a client find positioning opportunities. Upload competitor websites, their own materials, or a brief you’ve prepared to the Project first.
Based on the documents I've uploaded to this project, run a competitor gap analysis for [Client Name].
I want you to identify:
1. MESSAGING GAPS: What are competitors NOT saying that our client could own?
2. AUDIENCE GAPS: What buyer segments are competitors addressing poorly or ignoring?
3. FORMAT GAPS: What content formats are underused in this space?
4. CLAIM GAPS: What proof points or results could our client emphasize that competitors don't have?
Output format:
- Each gap as a separate entry
- For each: describe the gap, explain why it's an opportunity, and suggest one specific tactic to exploit it
- Mark each with confidence level: HIGH (clear from the documents) / MEDIUM (inference) / LOW (speculation)
If you need more information to make a confident assessment, tell me what's missing.Prompt 12: The Strategic Brief Generator
When to use it: When you need to turn a messy client intake conversation into a clean strategic brief you can share with a team or present back to the client for alignment.
I'm going to paste in my notes from a client discovery call. Turn them into a clean strategic brief using this structure:
STRATEGIC BRIEF STRUCTURE:
1. Business Context (2-3 sentences: what they do, where they are now)
2. The Core Problem (the real challenge behind what they said they want)
3. Success Criteria (what does "this worked" look like in 90 days?)
4. Target Audience (who specifically — be narrow, not broad)
5. Constraints (budget, timeline, internal politics, resources)
6. Recommended Focus Areas (top 3, with one sentence rationale each)
7. Open Questions (things I need to clarify before starting work)
RULES:
- Write in clear, jargon-free language
- If my notes contradict themselves, flag the contradiction instead of choosing one version
- Separate what the client said they want from what they actually need (if these differ)
DISCOVERY CALL NOTES:
[Paste notes here]Prompt 13: The Devil’s Advocate Review
When to use it: Before presenting a strategy or proposal to a client. This is one of the most valuable prompts in my workflow — it finds the holes before the client does.
I'm going to share a strategy/proposal I've written. Your job is to stress-test it.
Play devil's advocate. Do NOT tell me what's good about it. Only identify:
1. Assumptions I've made that might not hold true
2. Objections a skeptical client would raise
3. Scenarios where this approach could fail or underperform
4. Things I've left vague that will cause problems in execution
5. Anything a competitor or critic could use against this plan
For each issue: state the problem clearly, rate severity (High / Medium / Low), and suggest how to address it.
Be direct. I'd rather hear this now than in a client meeting.
STRATEGY/PROPOSAL:
[Paste document here]Prompt 14: The ICP Deep-Dive
When to use it: When a client says “our audience is everyone” and you need to push them toward specificity before producing any content or strategy.
Help me build a detailed Ideal Customer Profile (ICP) for [Client/Product Name].
Based on what I've told you about this business, push me toward specificity. For each section, give me:
- Your best initial answer based on available information
- The key question I need to answer to make this more accurate
- One way this assumption, if wrong, would break our marketing
SECTIONS:
1. Demographics & firmographics (B2B) or personal details (B2C)
2. The job-to-be-done (what outcome are they actually hiring this product/service to achieve?)
3. The trigger event (what happens in their life/business right before they start looking for this solution?)
4. Their current workaround (how are they solving this problem today without us?)
5. Their biggest fear about switching or trying something new
6. Where they consume information and who they trust
Available business info: [Paste what you know about the business here]Section 5: Editing and Quality Control Prompts
These are the prompts I use after drafts exist. The key here is being specific about what kind of editing you want — “make this better” produces mediocre results. Targeted editing prompts produce results you can actually use.
Prompt 15: The Targeted Line Edit
When to use it: When a draft is structurally sound but the writing quality needs tightening before it goes to a client.
Edit the following draft for quality. Your ONLY jobs are:
1. Cut any sentence that doesn't add information or move the reader forward
2. Replace weak verbs with specific, active ones (flag each change)
3. Fix any sentences that start with "This is" or "There are"
4. Identify and cut any repeated ideas (flag them before removing)
5. Check that every paragraph has a clear opening sentence that tells the reader what the paragraph is about
Do NOT:
- Change the argument or structure
- Rewrite sections from scratch
- Add new information I didn't include
- Change the tone or voice
Output the edited version in full, then list every change you made in a numbered changelog at the end.
DRAFT:
[Paste draft here]Prompt 16: The Tone Calibration Check
When to use it: When you’ve written something and it feels “off” but you can’t pinpoint why. Especially useful when writing in a client’s voice.
Analyze the tone of the following piece and compare it against the target tone description.
TARGET TONE: [e.g., "Confident and direct, like a senior practitioner talking to a peer — not a consultant explaining to a client, and not a blogger entertaining an audience"]
For each section of the piece, tell me:
1. Does the tone match the target? (Yes / Partially / No)
2. If not, what's off? (Too formal? Too casual? Too hedged? Too assertive?)
3. One specific rewrite example that would bring that section into alignment
Then give me an overall tone score (1-10 match with target) and the top 2 changes that would have the biggest impact.
PIECE TO ANALYZE:
[Paste content here]Prompt 17: The “Client-Ready” Final Check
When to use it: One final pass before sending anything to a client. This catches the stuff that slips through when you’ve been staring at a document too long.
Do a final pre-delivery check on the following document before I send it to a client.
Check for:
1. Any placeholder text left unfilled (look for brackets, TBDs, [X], etc.)
2. Factual claims that should be verified before publishing (flag them, don't remove)
3. Any sentence that could be misread or taken out of context in an embarrassing way
4. Formatting inconsistencies (heading styles, bullet formats, capitalization patterns)
5. The document's opening and closing — do they both deliver on what the title/brief promised?
Output: a numbered list of issues found. If you find nothing, say "No issues found" for each category explicitly — don't just skip it.
DOCUMENT:
[Paste document here]My Real-World Experience
A few months ago I had a situation that made me really appreciate what Claude Projects can do. I was juggling three active buyer clients at the same time — one looking for a holiday villa near Câmara de Lobos, one hunting for a long-term rental apartment in Funchal, and one considering commercial space in the Zona Velha. Each had completely different budgets, priorities, and communication styles. I kept a separate Project for each one in Claude, with a custom prompt at the top that described their profile, what they’d already seen, what they’d rejected and why, and their preferred tone for emails. Every time I sat down to write a follow-up or draft a WhatsApp message, Claude already knew the context. I didn’t have to re-explain anything.
Over 30 days of testing this workflow seriously, I tracked the time I was spending on client communications and property write-ups. I went from roughly 2.5 hours a day on that kind of writing work down to about 45 minutes. That’s not a rough guess — I kept a simple note in my phone each day. For a one-person operation where every hour either makes money or doesn’t, that’s the difference between having time to actually prospect and just treading water with admin.
The limitation that frustrated me most: the memory only lives inside the Project. If I accidentally started a new conversation outside of it, Claude had no idea who my client was or what we’d discussed. I did this twice in the first week, out of habit, and sent embarrassingly generic follow-ups before I caught myself. It’s not a dealbreaker, but it requires a discipline that took me a bit to build.
If this article carried a rating, I’d give Claude Projects a 4.5 out of 5 for solo real estate use — it genuinely replaces the role of an assistant who “knows your clients” without the cost of actually hiring one.
Bottom line: If you’re a solo agent managing multiple active clients and writing the same types of emails and descriptions over and over, Claude Projects will save you real hours every week. I’d recommend it without hesitation to any one-person real estate operation trying to stay organised and sound professional without burning out.
“`Section 6: Advanced Persistent Memory Prompts — Workflow Builders
These are the prompts that go beyond individual tasks. They’re designed to build reusable systems inside your Projects — the kind of setup that pays off over months, not just one session.
Prompt 18: The Project Memory Audit
When to use it: Every 30 days. This keeps your Project Instructions from becoming stale or bloated as your work evolves.
I'm going to paste in my current Project Instructions for this project. Audit them for me.
Tell me:
1. REDUNDANCIES: Anything that's repeated or that says the same thing in two different ways
2. CONTRADICTIONS: Any rules that conflict with each other
3. GAPS: Based on the work we've done in this project, what instructions are missing that would improve your outputs?
4. OUTDATED: Any references that seem stale based on how the work has evolved
5. CLARITY ISSUES: Any instruction that's ambiguous and could be interpreted multiple ways
Then give me a clean, rewritten version of the Project Instructions with all issues fixed.
CURRENT PROJECT INSTRUCTIONS:
[Paste your current instructions here]Prompt 19: The SOP Builder
When to use it: When you’ve done a task manually and want to document it as a repeatable process you can upload to future Projects. I use this constantly to build my personal SOPs library.
I'm going to describe a workflow I use repeatedly. Turn it into a formal SOP document I can upload to future Claude Projects as reference material.
WORKFLOW DESCRIPTION:
[Describe your process in plain language — it doesn't have to be organized]
Format the SOP as:
1. Purpose (one sentence)
2. When to use this SOP
3. What you need before starting (inputs, access, information)
4. Step-by-step process (numbered, with sub-steps where needed)
5. Quality checks at each stage
6. Common failure points and how to avoid them
7. Expected output / definition of done
Write it so clearly that someone who has never done this task before could follow it with no additional explanation from me.Prompt 20: The Multi-Project Context Bridge
When to use it: When you need to apply learnings from one client project to a new, similar one without starting from zero. This exports the relevant context in a portable format.
I'm starting a new project that's similar to work we've done in this project. Help me extract the most valuable context to carry over.
NEW PROJECT CONTEXT: [Brief description of the new project — industry, client type, goals]
From our work in this project, identify and summarize:
1. The most effective content angles that resonated (based on what we produced)
2. The stylistic rules that made the biggest difference to output quality
3. Any audience insights that would transfer to this new context
4. Mistakes or failed approaches to avoid repeating
5. Templates or formats that worked especially well
Output this as a "Project Starter Brief" I can paste into my new Project's instructions as a foundation.
Keep it under 400 words — it needs to be dense and usable, not exhaustive.Recommended tool: Make.com — connect 1,500+ apps and automate your workflows without code. Try it free →
Prompt 21: The Feedback Loop Processor
When to use it: After receiving client feedback. This converts subjective client reactions into specific, actionable instruction updates for your Project.
I received feedback from a client on work produced in this project. Help me turn it into better Project Instructions so this doesn't happen again.
CLIENT FEEDBACK (paste exactly what they said):
[Paste feedback here]
WHAT I PRODUCED (paste the relevant section):
[Paste the work they were reacting to]
Do the following:
1. Diagnose what specifically caused the disconnect between what I produced and
Robson Penassi
Real estate consultant in Madeira, Portugal. Solopreneur since 2012. Testing AI tools since 2023 to automate his one-person business. Writes about what actually works — and what does not.
More articles by Robson →