Install Skills in Your Platform
After purchasing the DTC Stack, download your files from the dashboard. Then install them in whichever AI platform you use.
Time to complete: ~5 minutes
What you're installing
Each skill is a SKILL.md file, a structured markdown document that tells the AI exactly how to execute a specific workflow. The Commerce Intelligence System (Brand Brain) is a folder of 55 files that all skills reference.
The DTC Stack also includes slash commands — pre-built shortcuts that let you run any skill by typing /skill-name in Claude Code. No prompt engineering, no manual file loading.
Your download contains:
dtc-stack/
├── .claude/commands/ # Slash commands (auto-detected by Claude Code)
│ ├── brand-brain.md
│ ├── customer-intelligence.md
│ ├── klaviyo-flow-architect.md
│ ├── klaviyo-campaign-engine.md
│ ├── product-page-engine.md
│ ├── shopify-page-builder.md
│ ├── dtc-ad-creative.md
│ ├── static-ad-prompt-engine.md
│ ├── landing-page-copy.md
│ ├── review-mining.md
│ ├── collection-seo.md
│ ├── geo-engine.md
│ ├── cro-audit.md
│ ├── cx-help-center.md
│ ├── social-ugc.md
│ ├── retention-optimizer.md
│ ├── blog-content.md
│ ├── pdp-seo.md
│ ├── competitor-intel.md
│ └── influencer-affiliate.md
├── skills/ # Skill definitions (the frameworks)
│ ├── commerce-intelligence-system/ # Brand Brain (55 files)
│ ├── customer-intelligence-engine/
│ ├── klaviyo-flow-architect/
│ ├── klaviyo-campaign-engine/
│ ├── product-page-engine/
│ ├── shopify-page-builder/
│ ├── dtc-ad-creative/
│ ├── static-ad-prompt-engine/
│ ├── landing-page-copy-system/
│ ├── collection-seo-builder/
│ ├── ecommerce-geo-engine/
│ ├── ecommerce-cro-audit/
│ ├── cx-ticket-help-center/
│ ├── review-mining-playbook/
│ ├── social-content-ugc-engine/
│ ├── retention-subscription-optimizer/
│ ├── ecom-blog-content/
│ ├── pdp-seo-optimizer/
│ ├── competitor-intel/
│ └── influencer-affiliate-engine/
├── brand/ # Your Brand Brain files (built with /brand-brain)
└── START_HERE.md # Quick start guide
Claude Code (Recommended)
Claude Code is the best way to run DTC Stack skills. Slash commands work out of the box — no configuration needed.
1. Create a project folder and move your files in
mkdir brand-ops && cd brand-ops
mv ~/Downloads/dtc-stack/* ./
Make sure the .claude/commands/ folder is included in your download. This is what enables the slash commands.
2. Launch Claude Code
claude
3. Run your first skill
Type / to see all available commands. Every DTC Stack skill is listed:
/brand-brain Build your Brand Brain (guided intake)
/customer-intelligence Pull live data from your ecommerce stack
/klaviyo-flow-architect Design email/SMS flows
/klaviyo-campaign-engine Plan campaign calendars and RFM segments
/product-page-engine Build a 9-section PDP
/shopify-page-builder Liquid sections from designs or wireframes
/dtc-ad-creative Generate ad copy
/static-ad-prompt-engine Image gen prompts for static ads
/landing-page-copy Advertorials, sales pages, quiz funnels
/review-mining Extract messaging from reviews
/collection-seo Optimize collection pages for search
/geo-engine Optimize for AI search engines
/cro-audit 12-module conversion audit
/cx-help-center Turn tickets into help articles
/social-ugc Social content and UGC playbooks
/retention-optimizer Subscription programs and cancel flows
/blog-content SEO blog content with product integration
/pdp-seo Product page SEO + Google Shopping feeds
/competitor-intel Competitor teardowns + counter-moves
/influencer-affiliate Creator pipeline + outreach sequences
Pick one and run it. Each command automatically loads the skill framework and reads your Brand Brain files for context.
4. Verify everything is working
/brand-brain
Claude should read the Commerce Intelligence System skill and start walking you through the Brand Brain setup. If it does, you're set.
No CLAUDE.md file needed. The .claude/commands/ folder handles everything — each slash command knows which skill to load and which Brand Brain files to read.
OpenClaw
1. Create a workspace
In OpenClaw, create a new workspace called "Brand Ops" (or your brand name).
2. Upload your files
Upload the entire dtc-stack/ folder contents to your workspace. Keep the folder structure intact - skills reference Brand Brain files by relative path.
3. Verify
Start a conversation and ask: "What skills are available?"
Cursor
1. Open the project
mkdir brand-ops && cd brand-ops
mv ~/Downloads/dtc-stack/* ./
Open this folder in Cursor: File → Open Folder
2. Create a .cursorrules file
Create .cursorrules in the project root:
This project contains the DTC Stack - a Brand Brain and 19 execution
skills for ecommerce content and operations.
The commerce-intelligence-system/ folder is the Brand Brain. Reference
it for all content generation: voice, positioning, personas, products,
objections, and guardrails.
When asked to run a skill, read the SKILL.md file from the relevant
skill folder and follow its framework exactly.
3. Verify
Open Cursor chat (Cmd+L) and type: "What skills do I have installed?"
Windsurf
1. Open the project
mkdir brand-ops && cd brand-ops
mv ~/Downloads/dtc-stack/* ./
Open in Windsurf: File → Open Folder
2. Create a .windsurfrules file
Create .windsurfrules in the project root:
This project contains the DTC Stack - a Brand Brain and 19 execution
skills for ecommerce content and operations.
The commerce-intelligence-system/ folder is the Brand Brain. Reference
it for all content generation: voice, positioning, personas, products,
objections, and guardrails.
When asked to run a skill, read the SKILL.md file from the relevant
skill folder and follow its framework exactly.
3. Verify
Open Cascade and type: "What skills do I have installed?"
File organization tips
Keep everything in one folder. Skills reference Brand Brain files by path. If you separate them, the AI won't find the context files.
Don't rename SKILL.md files. The frameworks reference themselves internally. Renaming can break cross-references.
Don't delete .claude/commands/. This folder powers the slash commands. Without it, you'd need to manually tell Claude which skill file to read.
You can add your own files. Drop customer reviews, competitor screenshots, existing copy, or analytics exports into the project folder. Skills can reference any file in the project — the more context, the better the output.
Team access: Your whole team can use the same installation. No per-seat limits. Just share the project folder (via Git, Dropbox, shared drive, etc.).
Next step
Now that skills are installed, the most important step: Build Your Brand Brain.