Claude Project: Your Always-On Brand Voice Assistant

What This Builds

A Claude Project pre-loaded with your brand voice guide, product catalog summary, tone rules, and customer persona, so every product description, email campaign, or customer response you generate automatically reflects your brand without re-explaining it every time. Instead of spending 10 minutes setting context before each AI session, you open one Project and your brand already lives there.

Prerequisites

• {{tool:Claude.plan}} subscription ({{tool:Claude.price}}). Projects require a paid account
• A working brand voice description (even informal notes work)
• Your product catalog (product names, categories, key features)
• 2-3 examples of content you love. emails, descriptions, or ad copy that sounds like your brand

The Concept

A Claude Project is like hiring an assistant who already knows your company from day one. You write their onboarding document once. your brand voice, your products, your rules, and then every conversation starts with that shared understanding. No more "we're an outdoor gear brand, we use casual language, we never say 'perfect'" at the start of every session.

Build It Step by Step

Part 1: Set Up the Project

1. Go to {{tool:Claude.url}} and sign in to your paid account
2. In the left sidebar, click Projects → Create Project
3. Name it something clear: "[Brand Name] Content Assistant" or "E-Commerce Copy HQ"
4. Click into the project. You'll see a Project Instructions panel on the right side

Part 2: Write Your Brand Brief (the most important step)

1. In the Project Instructions field, paste a comprehensive brand brief. Use this template:

## Who I Am
You are the content assistant for [Brand Name], an e-commerce brand selling [product category] to [customer description].

## Brand Voice
Our tone is: [adjective 1], [adjective 2], [adjective 3]
Examples of our tone done right: "[paste an example sentence or paragraph you love]"
Examples of what we NEVER sound like: "[paste something that sounds wrong for your brand]"

## Words and Phrases We Avoid
Never use: "perfect," "amazing," "game-changer," "revolutionary," [add your own]
Never describe products as "high quality" — be specific instead.

## Our Customers
[Describe your typical buyer: demographics, lifestyle, what they care about, how they shop]

## Product Categories We Sell
[List your main product categories with 1-line descriptions each]

## Key Policies (for customer service responses)
- Returns: [your policy]
- Refunds: [timeline]
- Shipping: [your typical carrier and delivery window]

## Content Rules
- Amazon listing bullets: start with capitalized benefit phrase, under 200 chars each
- Shopify descriptions: paragraph style, 100-150 words, end with brand tagline
- Emails: casual, direct, no more than 200 words for promotional campaigns
- Customer messages: empathetic, solution-first, under 100 words

1. Fill in every bracket. The more specific you are, the better every output will be.

Part 3: Upload Reference Documents

1. Click the Add Content button in the project
2. Upload or paste these documents (one file each):

• Product catalog: A simple CSV or text file with product name, SKU, description, and key features for each product
• Sample content: 3-5 pieces of content you're proud of. your best listings, your best emails, your best customer service responses
• "Never say" list: A text file of overused phrases, competitor terms to avoid, or anything that sounds off-brand

What you should see: Each document appears as a reference file in your Project. Claude has access to all of them in every conversation within this project. Troubleshooting: If uploads fail, paste the content directly into the Project Instructions instead, use clear headers to separate each document.

Part 4: Test and Refine

1. Start a new conversation inside the project (click New chat)
2. Ask for something you'd normally spend 10 minutes setting up context for:

• "Write a Shopify description for our new [product name]"
• "Draft an email campaign for our [upcoming promotion]"
• "Write 5 listing bullets for [product name]"

1. Review the output. Does it match your brand voice? Is it drawing on your product catalog correctly?

2. If not, refine the Project Instructions. Common fixes:

• Output is too formal → add "write as if speaking to a friend, not a business client"
• Output uses wrong product details → paste the correct details into the chat and also update the catalog file
• Output doesn't follow formatting rules → add explicit format examples to the instructions

Part 5: Make It Your Daily Driver

1. Bookmark the Project in Claude's sidebar
2. Every time you need content, open this Project (not a generic Claude chat)
3. Share the project with team members who create content (each person needs their own Claude account. you can't share project access)

Real Example: Using Your Project Daily

Setup: Your Project is configured for your home decor brand with a "warm, modern, slightly editorial" tone. Product catalog is uploaded. 12 example pieces of content are in the reference files.

Input (Monday morning): "I have 8 new candle SKUs arriving Thursday. Write Shopify descriptions for all of them. Here are the specs: [paste quick specs for each]"

Output: 8 distinct Shopify descriptions, each 100-150 words, in your brand voice, emphasizing sensory language and craftsmanship without using the word "perfect" once.

Time saved: Instead of 8 × 15 minutes = 2 hours of writing (or 8 × 5 minutes of AI sessions with context-setting), this takes 10 minutes total: 2 min to paste specs, 5 min for generation, 3 min to review.

Another use (Wednesday): "Our supplier just delayed a shipment. Write a proactive email to the 43 customers who ordered affected items. Reason: freight delay from overseas. New ETA: April 4. We want to include a 10% off next order code: PATIENCE10."

Output: A 150-word email draft in your brand voice, empathetic and apologetic without being alarming, with the code naturally integrated.

What to Do When It Breaks

• Output sounds generic or off-brand → Your Project Instructions are too vague. Add more specific examples of what "on-brand" sounds like.
• Wrong product details appearing → Your catalog file is outdated. Update it and re-upload.
• Claude can't access uploaded files → Paid feature limitation. Paste the relevant product info directly into your message: "The product is: [specs]."
• Team member's outputs sound different → Each person customizes their prompt style. Standardize by creating a team prompt template that everyone pastes into the project.

Variations

• Simpler version: Skip the file uploads. Just write a thorough Project Instructions brief, even 300 words of good context beats 30 minutes of setup in every session.
• Extended version: Create separate projects for different content types: "Customer Service Project," "Listing Copy Project," "Email Campaign Project", each with specialized instructions and examples.

What to Do Next

• This week: Build the project. Test it on 5 pieces of content you'd normally write manually.
• This month: Refine the instructions based on what sounds right vs. off. Add more product catalog details.
• Advanced: Connect Claude's API to Zapier or Make.com so content is generated automatically when new products are added to your Shopify catalog.

Advanced guide for e-commerce coordinator professionals. These techniques use more sophisticated AI features that may require paid subscriptions.