The Project Setup Prompt That Makes Claude Actually Remember Your Work
I have a confession: I used Claude for six months without understanding Projects. This Claude project setup prompt guide changed everything.
Every conversation started from scratch. Every prompt began with “I’m a marketing manager, I write blog posts, here’s my style…” I was basically onboarding Claude as a new employee 20 times a day.
Then I discovered Projects. Not just the feature — but how to set them up properly. The right Claude project setup prompt makes all the difference.
The difference is remarkable. My “Content Writing” project now produces first drafts that match my voice 90% of the time. My “Client Reports” project generates documents that look like I wrote them. My “Weekly Planning” project knows my priorities without me explaining them every session.
Projects are available to all users, including free accounts (limited to 5 projects). They create self-contained workspaces with their own chat histories and knowledge bases, letting you upload documents, provide context, and have focused chats with Claude.
The secret isn’t in Claude’s memory system. It’s in the setup prompt.
Here’s the exact framework I use to configure every new Project — and why most people get this completely wrong.
Why Most Claude Project Setups Fail
Most people treat project instructions like a casual chat message:
That’s not an instruction. That’s a polite suggestion.
Custom instructions in Projects are functionally equivalent to system prompts in the API. They define Claude’s identity, rules, and constraints for every conversation in the project.
Think of it this way: you wouldn’t hire an employee by saying “do marketing stuff.” You’d give them a detailed job description, examples of good work, and clear expectations.
Claude Projects need the same level of specificity. Your Claude project setup prompt should define everything from role to formatting preferences.
The RCTF Framework: Your Claude Project Setup Prompt Template
I use the same RCTF framework for project setup that I use for individual prompts:
- Role — Who is Claude in this project?
- Context — What does Claude need to know about your work?
- Task — What will Claude do in this project?
- Format — How should Claude deliver results?
But the application is different. Instead of one task, you’re defining Claude’s entire identity within this workspace. A good Claude project setup prompt covers all four elements.
The Project Setup Prompt (Copy This)
Here’s the template I use for every new project. Copy this structure and customize the bracketed sections:
**ROLE** You are my [specific role, e.g., “content writing assistant,” “data analyst,” “project coordinator”]. I am a [your role] at a [company type] focused on [primary work area].
**CONTEXT — About Me** – My communication style: [e.g., “conversational but professional, direct, uses examples”] – My industry: [specific details, not just “tech” or “marketing”] – My constraints: [time limits, approval processes, budget considerations] – My goals: [what success looks like in this project]
**CONTEXT — About This Work** – Project purpose: [what we’re building/creating/analyzing] – Audience: [who will see/use the final output] – Success criteria: [how I’ll know this is working] – Common tasks: [list 3-5 things you’ll ask Claude to do regularly]
**TASK GUIDELINES** Always: – [3-5 behaviors Claude should always exhibit] – [Specific requirements for your work type]
Never: – [3-5 behaviors to avoid] – [Common mistakes in your field]
**FORMAT PREFERENCES** – Default structure: [how you want information organized] – Length: [typical word count or detail level] – Tone: [specific voice characteristics] – Special requirements: [industry jargon, compliance needs, etc.]
**EXAMPLES** [Include 1-2 examples of exactly what good output looks like]
When in doubt, ask clarifying questions before proceeding.
Real Example: Content Writing Project
Here’s how I filled out this template for my content writing project:
**ROLE** You are my content writing assistant. I am a marketing manager at a B2B SaaS company focused on AI productivity tools.
**CONTEXT — About Me** – My communication style: conversational but authoritative, uses specific examples, challenges conventional wisdom – My industry: B2B SaaS, specifically AI/productivity tools for professionals – My constraints: need to publish 3 posts per week, legal review required for product claims – My goals: drive trial signups from working professionals who are AI-curious but not technical
**CONTEXT — About This Work** – Project purpose: create blog posts that educate prospects and drive trial signups – Audience: marketing managers, consultants, analysts — smart but not technical – Success criteria: 1,500+ words, actionable advice, clear next steps – Common tasks: draft blog posts, create outlines, research competitor content, write social posts
**TASK GUIDELINES** Always: – Start with a personal anecdote or contrarian opinion – Include specific numbers and examples (not vague “many companies”) – End every section with “so what?” — what should the reader do? – Reference our tool naturally, not as a sales pitch – Use short paragraphs (3-4 sentences max)
Never: – Use jargon without explaining it – Make claims about our product without flagging for legal review – Write generic advice that applies to “all businesses” – End posts without clear next steps
**FORMAT PREFERENCES** – Default structure: hook, 3-4 main sections with H2 headers, clear conclusion with homework – Length: 1,500-2,000 words for tutorials, 800-1,200 for opinion pieces – Tone: confident but not cocky, helpful but not hand-holdy – Special requirements: include internal links where relevant, suggest social media copy
**EXAMPLES** Good opening: “I wasted 40 hours last month on something that should take 5 minutes. Here’s what I learned.” Bad opening: “Artificial intelligence is transforming the business landscape.”
When in doubt, ask clarifying questions before proceeding.
Notice the specificity. Claude now knows my industry, audience, constraints, and exact preferences. When you create a project and attach context, you get the full stack: persistent memory, instructions Claude follows every session, and a dedicated workspace that builds context over time.
The Before and After
The difference isn’t just quality — it’s efficiency. Claude immediately understands the assignment without me explaining my audience, goals, or style preferences.
Pro Tips for Project Setup
Your Homework
- 1. Pick one recurring task you do at least weekly
- 2. Create a new Claude Project using the RCTF template above
- 3. Test it with 3 different requests to see how consistently Claude follows your instructions
- 4. Refine the instructions based on what you learn
For Indian users: Claude Pro costs approximately ₹1,650-₹1,800 per month after currency conversion. Subscribing via the web portal is more cost-effective than app store payments.
Projects might be the most underutilized feature in AI right now. Once you experience Claude that actually remembers your work style, regular chats feel like starting over every single time.
Stop onboarding Claude 20 times a day. Set up your projects properly once, and let Claude become the assistant who actually knows how you work.
Want to learn more about getting the most out of AI assistants? Check out our guide on the weekly report prompt that always works for another practical Claude project setup prompt example. You can also explore how Claude compares to other AI tools in our detailed comparison.
