How to Use Claude Projects with Custom Instructions and Knowledge Files to Build a Brand Voice Assistant
Build a Persistent Brand Voice Assistant with Claude Projects
Marketing teams struggle with consistency. Every piece of content—emails, social posts, landing pages—needs to sound like it came from the same voice. Claude Projects solves this by letting you create a persistent AI workspace loaded with your brand guidelines, style guides, and reference materials. Instead of re-explaining your brand in every conversation, you configure it once and your entire team benefits. This guide walks you through setting up a Claude Project that acts as a dedicated brand voice assistant, complete with custom instructions, uploaded knowledge files, and team collaboration workflows.
Prerequisites
- A Claude Pro, Team, or Enterprise plan (Projects require a paid plan)- Your brand style guide document (PDF, TXT, or DOCX format)- Existing content samples that exemplify your brand voice (at least 5–10 pieces)- Access to the Claude web interface at
claude.ai
Step-by-Step Setup
Step 1: Create a New Project
- Log in to claude.ai and click Projects in the left sidebar.- Click Create Project and name it something descriptive, such as
Brand Voice Assistant – [Your Company].- Add a description: “Persistent brand voice assistant for the marketing team. Generates on-brand content across all channels.”
Step 2: Upload Knowledge Files
Knowledge files give Claude persistent context about your brand without eating into your conversation’s context window. Upload the following:
| File Type | Example Filename | Purpose |
|---|---|---|
| Brand Style Guide | brand-style-guide-2026.pdf | Tone, voice attributes, do's and don'ts |
| Content Samples | approved-blog-posts.txt | Examples of on-brand writing |
| Terminology Glossary | glossary-and-naming.csv | Product names, banned words, preferred terms |
| Audience Personas | buyer-personas.pdf | Target audience profiles and messaging angles |
| Competitor Positioning | competitive-messaging.docx | Differentiation points and claims to avoid |
Step 3: Write Custom Instructions
Custom instructions are the core of your brand voice assistant. Click Edit Project Instructions and paste a structured prompt like the following:
You are the official brand voice assistant for [Company Name].
CORE VOICE ATTRIBUTES:
- Tone: Confident but approachable. Never arrogant.
- Style: Clear, concise, jargon-free. Favor active voice.
- Personality: Helpful expert who simplifies complex topics.
RULES:
- Always refer to the uploaded brand style guide before generating content.
- Use approved terminology from the glossary. Never use banned terms.
- Match content to the specified audience persona when one is provided.
- Default to the “Marketing Professional” persona if none is specified.
- Include a CTA in every piece of content unless told otherwise.
- Keep paragraphs under 3 sentences for digital content.
- Do not make claims about competitors by name unless referencing the competitive positioning document.
OUTPUT FORMAT:
- Start every response with a one-line summary of what you produced.
- End with a “Brand Check” section listing: tone score (1-5), terminology compliance (pass/fail), and any flags.
When asked to review existing content, provide specific line-level feedback referencing the style guide.
Step 4: Test with Real Scenarios
Start a new conversation inside your project and run through common marketing tasks:
Prompt: "Write a LinkedIn post announcing our new API integration
with Salesforce. Target audience: enterprise IT leaders.
Keep it under 200 words."
Verify the output against your style guide. Then test a review scenario:
Prompt: "Review this email subject line for brand compliance:
'You NEED to see this!! Revolutionary AI that will BLOW YOUR MIND'"
Claude should flag the all-caps, hyperbolic language, and exclamation marks based on your uploaded guidelines.
Step 5: Invite Your Team
On Team and Enterprise plans, click the Share button in your project and invite team members by email. Everyone who joins the project gets access to the same knowledge files and custom instructions, ensuring consistent outputs across the team.
Step 6: Integrate with the API (Optional)
For programmatic access, use the Claude API with system prompts that mirror your project instructions:
import anthropic
client = anthropic.Anthropic(api_key=“YOUR_API_KEY”)
brand_system_prompt = open(“brand-instructions.txt”).read()
message = client.messages.create(
model=“claude-sonnet-4-6”,
max_tokens=1024,
system=brand_system_prompt,
messages=[
{
“role”: “user”,
“content”: “Write a product launch email for our Q2 feature release. Audience: existing customers.”
}
]
)
print(message.content[0].text)
Install the SDK first:
pip install anthropic
Pro Tips for Power Users
- Version your instructions: Keep a dated changelog at the top of your custom instructions so team members know what changed and when.- Create sub-projects by channel: Make separate projects for Email, Social Media, and Blog content. Each inherits the core brand guide but has channel-specific instructions (character limits, hashtag rules, etc.).- Use starred conversations: Star conversations that produced exceptional outputs. They serve as reference points for the team.- Prompt templates: Include reusable prompt templates directly in your custom instructions using a labeled format like
[TEMPLATE: Product Launch Email]so any team member can invoke them by name.- Structured glossary files: Format your glossary as CSV with columns forapproved_term, banned_alternatives, context_note. Claude parses structured data more reliably than prose.- Periodic knowledge refresh: Update uploaded files quarterly to reflect new products, updated messaging, and retired campaigns.
Troubleshooting Common Issues
| Problem | Cause | Solution |
|---|---|---|
| Claude ignores the style guide | Instructions are too vague or buried in long text | Move the most critical rules to the top of your custom instructions. Use numbered rules and bold key terms. |
| Outputs sound generic | Not enough exemplar content uploaded | Upload 10+ approved content samples. Include a mix of channels (email, blog, social). |
| Knowledge file upload fails | File exceeds size limit or is in unsupported format | Convert to PDF or TXT. Split large files into smaller chunks under 10MB each. |
| Team members see different behavior | Conversations started before instruction updates | Start a new conversation after updating project instructions. Existing threads use the instructions from when they were created. |
| API responses differ from web UI | System prompt doesn't match project instructions | Export your project instructions and use them verbatim as the API system prompt. |
Can I use Claude Projects on the free plan?
No. Projects are available on Claude Pro ($20/month), Team ($30/user/month), and Enterprise plans. The free tier does not support Projects, custom instructions, or knowledge file uploads. If you only need basic brand guidance, you can manually paste a shorter system prompt at the start of each conversation, but you lose persistence and team sharing.
How many knowledge files can I upload to a single project?
Claude Projects support a combined knowledge base of approximately 200,000 tokens, which is roughly equivalent to 500 pages of text. There is no hard limit on the number of individual files, but each file must be under the per-file size limit. For best results, consolidate related content into fewer, well-organized files rather than uploading dozens of small fragments.
Will Claude always follow my custom instructions exactly?
Claude treats custom instructions as strong guidance, but very long or contradictory instructions may cause inconsistencies. To maximize compliance, keep instructions concise and prioritized, put the most important rules first, and test edge cases before rolling out to the full team. Including explicit examples of desired and undesired outputs directly in your instructions significantly improves adherence.