Run Your First Skill
Your Brand Brain is built and your skills are installed. Let's run one and see the difference.
Time to complete: ~15 minutes for your first full skill run
Which skill to start with
Pick based on your most urgent need:
| If you need... | Start with | Why |
|---|---|---|
| Product pages | Product Page Conversion Engine | Highest-impact, most visual result |
| Email flows | Email Flow Architect | See full flows generated with your voice |
| Ad copy | DTC Ad Creative System | Quick output, easy to compare against current ads |
| A quick win | Review Mining Playbook | Just feed it reviews - no Brand Brain required |
| SEO content | Collection SEO Builder | Generates full collection page copy |
For this walkthrough, we'll use the Product Page Conversion Engine - but the process is the same for any skill.
Step 1: Run the skill
In Claude Code, type the slash command:
/product-page-engine
That's it. Claude loads the skill framework, reads your Brand Brain files for context, and asks you for inputs. No file paths to remember, no prompt to construct.
Step 2: Provide the inputs
Each skill has an intake section that asks for specific information. For the Product Page Engine, you'll need:
- Product name
- Product URL (if it already exists on Shopify)
- Key features (or tell the AI to pull from
products_overview.md) - Target persona (or tell the AI to pull from
personas.md) - Awareness level of the target audience (unaware, problem-aware, solution-aware, product-aware, most-aware)
Here's what that looks like in practice:
Product: Collagen Peptides (Unflavored)
URL: https://our-store.com/products/collagen-peptides
Target persona: "Active Sarah"
Awareness level: Solution-aware (she knows collagen helps, doesn't know our brand)
You don't need to tell Claude which Brand Brain files to read — the slash command handles that automatically. It pulls from your voice, personas, objections, and product files.
Step 3: Review the output
The Product Page Engine generates a full 9-section PDP:
- Above the fold - headline, subheadline, primary CTA
- Social proof bar - review count, star rating, trust signals
- Problem/Solution - the pain point this product solves
- Features → Benefits - what it does, mapped to what they care about
- How it works - usage instructions, ritual positioning
- Objection handling - directly addresses why someone might hesitate
- Social proof deep-dive - customer quotes, before/after, UGC
- FAQ - most common pre-purchase questions
- Final CTA - urgency, guarantee, last push
Check each section against your Brand Brain:
- Does it sound like you? Compare to
voice_and_tone.mdexamples - Does it address real objections? Cross-reference with
objections.md - Is it accurate about the product? Check against
products_overview.md - Does it respect guardrails? Any compliance issues from
guardrails.md?
Step 4: Iterate
The first output won't be perfect. That's normal - and it's fast to improve.
Common adjustments:
"The tone is too formal"
→ Update voice_and_tone.md with more examples of how you actually sound. Then re-run.
"It's making claims we can't make"
→ Add those specific restrictions to guardrails.md. Then re-run.
"It missed a key selling point"
→ Add it to products_overview.md in the features-to-benefits section. Then re-run.
"The objection handling feels weak"
→ Add more detail to the specific objection in objections.md - include the proof point or customer quote that overcomes it. Then re-run.
Each iteration makes the Brand Brain stronger. The second product page will be better than the first. The tenth will be significantly better.
Step 5: Use the output
Once you're happy with the copy:
- Copy the sections into your Shopify product page editor
- Format for your theme - adjust headings, spacing, and section structure to match your Shopify theme
- Add visuals - the skill generates copy, not images. Add product photos, lifestyle shots, and UGC to the appropriate sections
- Review once more in context - copy reads differently on a live page than in a text editor
Running other skills
The process is identical for every skill — type the slash command, provide inputs, review output:
| Need | Command |
|---|---|
| Email flows | /klaviyo-flow-architect |
| Email campaigns | /klaviyo-campaign-engine |
| Ad copy | /dtc-ad-creative |
| Landing pages | /landing-page-copy |
| Review mining | /review-mining |
| Collection SEO | /collection-seo |
| GEO optimization | /geo-engine |
| CRO audit | /cro-audit |
| Help center | /cx-help-center |
| Social/UGC | /social-ugc |
| Retention | /retention-optimizer |
| Blog content | /blog-content |
| PDP SEO | /pdp-seo |
Some skills have additional inputs:
/klaviyo-flow-architectasks for trigger events, timing preferences, and A/B test ideas/dtc-ad-creativeasks for platform (Meta/Google), awareness level, and current offers/cro-auditasks for your current conversion rate and top landing pages/review-miningjust needs a batch of customer reviews — paste them in or point to a CSV
Tips for better outputs
Give more context, get better output. Drop customer reviews, competitor pages, or analytics screenshots into your project folder. Tell the skill to reference them.
Run related skills together. If you're launching a product, run Product Page → Ad Creative → Klaviyo Flow in sequence. They'll all reference the same Brand Brain, so the messaging will be consistent across channels.
Keep updating your Brand Brain. Every time you spot something off in a skill output, it means a Brand Brain file needs more detail. Update it. The system gets smarter every time you use it.
Don't edit the SKILL.md files. These are the frameworks - they're designed to work as-is. Customize your output by enriching the Brand Brain, not by modifying skill files.
What success looks like
After running 3-5 skills, you should notice:
- Output sounds like your brand without heavy editing
- Objections are addressed naturally, not awkwardly inserted
- Product descriptions are specific, not generic
- Copy across channels (email, product pages, ads) feels consistent
- You're spending minutes generating what used to take hours
If you're not seeing this, the Brand Brain needs more detail. Go back to Build Your Brand Brain and enrich the files that feel thin.