The Transformation Starts Here
Purium's mission is pure, premium nutrition that transforms people from the inside out. Our goal with AI is the same: not surface-level shortcuts, but deep capability that compounds over time. Today you'll learn to use Claude in a way that actually reflects who Purium is.
The Five Prompting Philosophies
Most people use Claude the way they used Google: type a quick question and hope for the best. That's one way to use it. It's also the least powerful way. There's a full spectrum of approaches, each unlocking a deeper level of collaboration. Understanding where you are on this spectrum is the first step to leveling up.
The R-C-T-F-C Formula: Prompt Engineering Made Simple
- RRole: "You are a Purium Brand Partner coach specializing in onboarding new members..." — Sets vocabulary, judgment, and tone in one line.
- CContext: Who is the audience? What's the situation? What has already been decided? Don't make Claude guess what you know about Purium.
- TTask: "Write three email subject lines for our Ultimate Lifestyle Transformation program" beats "help with marketing."
- FFormat: "Give me three numbered options, under 60 characters each." Prevents reformatting work later.
- CConstraints: "Do not make any health claims. Do not use the word 'detox' without qualification. Always include our FDA disclaimer language."
Before vs. After: Purium Style
Three Habits to Build Starting Today
- Give Claude a role first. Start with "You are a [role] for Purium..." and every output immediately gets better.
- Iterate, don't restart. If the output is close: "This is good. Now make it warmer, shorten by 20%, and move the CTA to the second paragraph." Claude holds the full conversation context.
- Paste examples. "Write in the style of this email I love: [paste]." Claude will match cadence, structure, and feel.
"What else would you like to ask me to make this the most optimal and effective?"
or, when launching a complex task:
"What questions do you have about this request to execute it at a high level?"
This is the exact prompt used to turn a Zoom transcript into a full Purium branded webpage (see the Content Creation use case below). Claude asked clarifying questions, the brief got sharper, and the output needed far less editing. Make this a habit for any high-stakes or complex task.
Purium sells supplements and superfoods. All copy must include FTC/FDA-compliant language. Always instruct Claude to follow these rules in your prompts. Make this part of your Project instructions so it fires automatically.
Building Your Brand Documents
The single biggest unlock for getting consistent, on-brand Claude output is not better prompting: it's better context files. When you upload a Brand Voice document or a Brand Guidelines reference into a Claude Project, Claude reads it before every conversation inside that project. You stop re-explaining. Claude already knows.
These are the documents worth creating now. Each one takes 30-60 minutes to build and saves hours every week.
Brand Voice Document
- How Purium sounds in writing (3-5 adjectives + explanation)
- What the brand never says or sounds like
- Tone shifts by platform (Instagram vs. email vs. formal letter)
- Power words Purium uses (transformation, pure, premium, nourish, thrive)
- Words to avoid ("detox" without context, disease claims, hype language)
- 2-3 examples of ideal Purium copy with annotations
Brand Guidelines Document
- Mission: "Pure + Premium" nutrition for transformation
- Core values (6 Purium core values)
- Visual direction notes (color palette, logo usage rules)
- Product naming conventions (exact spelling, capitalization)
- Platform-specific formatting rules
- Legal/compliance requirements per content type
Product Reference Sheet
- Full product list with correct names and capitalization
- Key benefits per product (Power Shake, Biome Medic, Super Amino 23, Sleep Nightly, Alpha Omega, etc.)
- Program structures (Ultimate Lifestyle Transformation 12-Week, LTD Lifestyle Transformation Daily)
- Approved benefit language per product
- Ingredients to highlight per product
- Claims to never make per product
Audience Persona Document
- Primary customer persona (health-conscious adult, 35-55)
- Brand Partner persona (values-aligned, entrepreneurial)
- Pain points for each audience
- Language each audience uses about their goals
- Objections each audience has before buying
- What makes each persona say yes
Compliance + Claims Guide
- FDA disclaimer (full, approved text)
- List of approved structure/function claims
- Prohibited disease claims by product category
- Testimonial usage rules
- Income disclosure requirements for Brand Partner content
- Platform-specific restrictions (Facebook, Instagram, email)
Brand Partner Program Guide
- Program tiers and titles (Diamond, Black Diamond, Red Diamond, Crown)
- Compensation structure overview
- Approved language for income opportunity discussions
- Onboarding steps and resources
- Support resources Brand Partners have access to
- Key messaging for recruiting vs. product sharing
How to Build These Documents Using Claude
You don't have to write these from scratch. Claude can help you create them. Use this to get started:
Projects: Claude's Long-Term Memory
By default, Claude remembers nothing between conversations. Every new chat is a blank slate. If you've been pasting your brand context or product details every single time, that's the cost of not using Projects. A Project is a persistent workspace where Claude always knows your context, your files, and your preferences.
What Lives Inside a Project
- 1Instructions (System Prompt): What Claude should always know before any conversation inside this project. Your brand voice, audience, compliance rules, and formatting preferences. Set it once; it fires every time.
- 2Knowledge Files: Upload your Brand Voice doc, Product Reference Sheet, Compliance Guide, Brand Partner Program overview. Claude reads all of them and references them throughout every conversation.
- 3Persistent Context: Chats inside the project share history. Refer back to previous decisions without re-explaining them.
Sample Project Instructions: Purium Marketing
Purium Project Ideas for Your Team
Other Corporate Use Cases
These prompt structures support team members working on curriculum, technical communications, and formal correspondence.
📚 Training Curriculum
🖥️ Developer Briefs
✉️ Letters + Comms
Marketing Use Cases: Ready to Copy
Transformation Program Launch
Repurpose Blog to Social
New Partner Welcome
Zoom Transcript → Webpage
Claude Models: Choosing the Right Tool
Not all versions of Claude are the same. Anthropic offers a family of models, each built for different levels of complexity and speed. Think of it like Purium's programs: LTD handles your everyday nutritional foundation; the 12-Week ULT is for a deeper transformation. Each serves a different need.
- Quick subject line suggestions
- Simple formatting tasks
- Lookup-style questions
- High-volume, templated outputs
- Chatbot or customer FAQ responses
- Marketing copy and campaigns
- Brand Partner communications
- Email sequences
- Social content creation
- Training curriculum drafts
- Developer briefs and letters
- Strategic planning documents
- Complex multi-part analysis
- Legal or compliance review support
- Long-form curriculum design
- Sensitive executive communications
- Research synthesis across many sources
Skills: Extending Claude's Capabilities
Skills (also called integrations or tools) are add-ons that let Claude take actions beyond conversation: searching the web, pulling live data, connecting to apps, running code. They are powerful. They also carry real risk when they come from unknown sources.
Non-Negotiable: Skills Safety at Purium
Third-party Skills can request access to your Claude conversations, your files, and your connected accounts. An unknown Skill could be designed to exfiltrate business-sensitive data or inject hidden instructions into Claude that you never see.
- Third-party Skills may have access to everything you type in Claude
- Malicious Skills can execute "prompt injection" — hidden instructions that override yours
- Skills with access to our systems could expose customer data or Brand Partner information
- A compromised Skill could post, send, or modify things on your behalf
The rule is simple: only install Skills verified by Anthropic, or explicitly approved by leadership. When someone sends you a link to install a Skill — ask first. No exceptions.
Safe, Built-In Capabilities (No Third-Party Risk)
These come from Anthropic directly and are safe to use in Claude.ai:
(2) What data is it requesting access to?
(3) Has leadership approved this for Purium team use?
If you cannot confidently answer all three: do not install it. Come ask first.
Evaluations: How Do You Know It's Actually Working?
Getting Claude to produce output is easy. Knowing whether that output is actually good, consistently, over time, across different team members, is a different skill entirely. That's what evaluations are for.
An evaluation (or "eval") is simply a structured way of asking: did this output meet the standard? It can be as simple as a checklist you run before publishing, or as sophisticated as a scoring rubric that multiple team members use to compare Claude's output across different prompt versions.
The Three Levels of Evaluation
-
1Gut Check (30 seconds): Read it out loud. Does it sound like Purium? Does it feel warm, credible, and clear? Would you personally share this? If anything makes you hesitate, flag it before it ships.
-
2Criteria Check (2 minutes): Run the output against a fixed set of standards: on-brand voice, correct product names, no discontinued items, compliance language present, CTA points to the right next step, no disease claims. This is where a checklist saves you.
-
3Comparative Eval (ongoing): When you want to improve a prompt or template, run two versions against the same brief and score them side by side. Which one converts better? Which one sounds more like Purium? This is how you compound quality over time.
Ask Claude to Evaluate Its Own Output
One of the most powerful and underused techniques: after Claude produces a draft, ask it to evaluate the draft before you do. Claude will often catch its own weaknesses faster than you will.
Evaluate a Prompt, Not Just an Output
If Claude consistently gives you mediocre results on a particular type of asset, the problem is usually the prompt, not the model. Use this technique to diagnose and improve:
The Purium Output Scorecard
A simple rubric your team can use consistently. Print it, paste it in your Project, or check it mentally before anything goes out.
Green Light: Ship It
- Sounds unmistakably like Purium
- Written for the right audience at the right stage
- CTA is clear and points to the logical next step
- No disease claims, compliance language present
- All product names current and correctly spelled
- You'd personally share or send this
Red Flag: Revise Before Sending
- Sounds generic, corporate, or over-hyped
- Audience is unclear or mixed
- CTA is vague ("learn more," "click here" with no context)
- Contains a claim that could be read as a disease cure
- References a discontinued product
- You'd hesitate to put Purium's name on it
Hands-On Practice
Open Claude now. Choose the exercise that fits your role and work through it at your own pace.
Wrap-Up
The Four Things That Will Actually Change How You Work
- 1Move up the prompting spectrum. The difference between Search Engine Mode and Intent Engineering is the difference between generic output and output that sounds like Purium. Invest 60 seconds more per prompt; save 20 minutes of editing.
- 2Build your brand documents and upload them to Projects. Once you have a Brand Voice doc, a Product Reference Sheet, and a Compliance Guide inside your Claude Project, every output gets better automatically. This is the highest-leverage hour you can invest.
- 3Ask Claude what it needs before it starts. On any complex task, end your brief with "What questions do you have to execute this at a high level?" You'll get sharper output with less back-and-forth.
- 4Evaluate before you publish. Run the scorecard. Ask Claude to self-evaluate. Every output you improve raises the floor for the next one. This is where the compound effect kicks in.