Claude Projects Playbook: 11 Prompts to Build Custom AI Assistants for Every Business Function
This Claude Feature Eliminates the #1 AI Frustration
Learn to build custom AI assistants with Claude Projects. 11 copy-paste prompts to create specialized tools that remember your business context.
Hey there!
You’re tired of re-explaining your business context to Claude in every single conversation. You waste 10 minutes setting up each chat with background, preferences, and what you actually need. Then you close the tab and start over tomorrow.
Claude Projects fixes this. Think of it as building your own team of specialized AI assistants, each one pre-loaded with your knowledge, trained on your style, and ready to work the second you open it.
Here’s what you’re getting: 11 prompts to build custom AI assistants for sales, content, research, analysis, or whatever your business needs. Plus templates to maintain them long-term.
Why Projects Beat Regular Chats
Standard Claude conversations forget everything. Projects remember.
You upload your brand guidelines once, write your custom instructions once, and that assistant is ready forever. No more copying and pasting the same context every morning.
The difference? A generic chat takes 10 minutes to warm up. A properly configured Project starts working in 10 seconds.
Let’s build your custom assistants.
Prompt #1: Define Your Assistant’s Core Role
What it does: Creates a clear role definition that guides all of the Project’s responses
When to use it: Starting any new Claude Project, before you add any knowledge or instructions
The Prompt:
I’m creating a Claude Project for [SPECIFIC BUSINESS FUNCTION]. Help me define its core role.
Answer these questions in a structured format I can use as the foundation:
1. Primary function (what does this assistant DO)
2. Key responsibilities (3-5 specific tasks)
3. Decision-making authority (what can it decide vs. what needs my input)
4. Success metrics (how do I know it’s working)
5. Boundaries (what it should NOT do or handle)
My business context: [YOUR INDUSTRY/COMPANY]
This assistant will primarily help with: [MAIN USE CASE]How to use it:
Replace [SPECIFIC BUSINESS FUNCTION] with your actual need (e.g., “sales outreach,” “content editing,” “competitive research”)
Fill in your industry and main use case
Copy the output directly into your Project’s planning document
Example input:
“I’m creating a Claude Project for social media content creation. Help me define its core role.
Answer these questions in a structured format I can use as the foundation:
Primary function (what does this assistant DO)
Key responsibilities (3-5 specific tasks)
Decision-making authority (what it can decide vs. what needs my input)
Success metrics (how do I know it’s working)
Boundaries (what it should NOT do or handle)
My business context: B2B SaaS company selling project management tools. This assistant will primarily help with: Creating LinkedIn posts and Twitter threads.”
What you’ll get: A structured role definition covering function, responsibilities, decision authority, success metrics, and boundaries
Pro tip: Keep this document in your Project’s knowledge base as “assistant_role.md” - Claude will reference it automatically in every conversation.
Prompt #2: Generate Custom Instructions
What it does: Converts your role definition into actual custom instructions Claude understands
When to use it: Right after defining the role, before you start using the Project
The Prompt:
Convert this role definition into custom instructions for a Claude Project:
[PASTE YOUR ROLE DEFINITION FROM PROMPT #1]
Format the instructions as:
- Clear “You are” statements defining identity
- Specific response patterns (how to structure outputs)
- Tone and style requirements
- Default behaviors (what to do without being asked)
- Constraints (what to avoid)
Make instructions specific enough that someone else could use this Project and get consistent results.How to use it:
Copy your role definition from Prompt #1
Paste it into the prompt
Take the output and add it to your Project’s custom instructions field
Example input:
“Convert this role definition into custom instructions for a Claude Project:
Primary function: Create engaging LinkedIn and Twitter content for B2B SaaS audience Key responsibilities: Draft posts, suggest hooks, optimize for engagement, repurpose content Decision authority: Can choose formats and hooks; needs approval on claims about product features Success metrics: Posts require minimal editing, hooks generate clicks, tone matches brand Boundaries: No promotional spam, no unverified claims, no engagement bait tactics”
What you’ll get: Formatted custom instructions ready to paste into your Project settings
Pro tip: Test the instructions in 3-4 conversations before finalizing them. You’ll spot gaps fast.
Prompt #3: Create a Knowledge Base Audit
What it does: Identifies exactly what documents and data your Project needs to be effective
When to use it: Before uploading files randomly—this prevents knowledge base bloat
The Prompt:
I’m building a Claude Project for [ROLE/FUNCTION]. Help me identify the essential knowledge base documents.
Current role: [PASTE ROLE FROM PROMPT #1]
Create a prioritized list:
TIER 1 - Critical (Project can’t function without these):
- Document type
- Why essential
- Update frequency
TIER 2 - Important (Significantly improves output):
- Document type
- Why valuable
- Update frequency
TIER 3 - Optional (Nice to have):
- Document type
- Benefit
- Update frequency
Include document naming conventions and organization structure.How to use it:
Fill in your role/function
Paste your role definition from Prompt #1
Use the output as your upload checklist
Example input:
“I’m building a Claude Project for social media content creation. Help me identify the essential knowledge base documents.
Current role: Create engaging LinkedIn and Twitter content for a B2B SaaS audience selling project management tools.”
What you’ll get: Prioritized list of exactly what documents to upload, organized by importance and update frequency
Pro tip: Start with only Tier 1 documents. Add Tier 2 after you’ve used the Project for a week and know what’s actually missing.
Prompt #4: Build Conversation Starters
What it does: Creates click-and-go prompts that appear when you open your Project
When to use it: After your custom instructions are set—these become your quick-launch buttons
The Prompt:
Create 5 conversation starters for a Claude Project focused on [ROLE/FUNCTION].
For each starter, write:
- A clear action-focused title (what the user wants to accomplish)
- A complete prompt that Claude can immediately execute
- Any placeholders the user needs to fill
Requirements:
- Cover the most common 5 use cases for this role
- Each starter should produce output in under 2 minutes
- Make them specific enough that output requires minimal editing
Project role: [PASTE ROLE FROM PROMPT #1]How to use it:
Replace [ROLE/FUNCTION] with your specific Project focus
Paste your role definition
Add the starters to your Project settings
Example input:
“Create 5 conversation starters for a Claude Project focused on B2B social media content creation.
For each starter, write:
A clear action-focused title (what the user wants to accomplish)
A complete prompt that Claude can immediately execute
Any placeholders the user needs to fill
Requirements:
Cover the most common 5 use cases for this role
Each starter should produce output in under 2 minutes
Make them specific enough that the output requires minimal editing
Project role: Create engaging LinkedIn and Twitter content for a B2B SaaS audience selling project management tools.”
What you’ll get: 5 ready-to-use conversation starters with complete prompts and placeholder guidance
Pro tip: Update these monthly based on which ones you actually use. Delete starters that sit idle.
The Advanced System
You just got 4 prompts that’ll create a functional Claude Project in under an hour.
But there’s a difference between a Project that works and one that transforms how you work. The kind where you wonder how you survived without it.
The next 7 prompts handle the advanced setup:
Workflow prompts that chain multiple tasks automatically
Testing frameworks to catch issues before they cost you time
Maintenance systems so your Project improves instead of decaying
Plus: Multi-project strategies for building an entire AI team