Marketing Content Strategy
Create compelling, conversion-focused marketing copy based on customer pain points, JTBD framework, and competitive advantages. Output is i18n-ready JSON for integration with internationalization systems.
Commands
| Command |
Description |
/creo content landing |
Generate landing page content |
/creo content feature |
Generate feature page content |
/creo content pricing |
Generate pricing page content |
/creo content <page-type> |
Generate content for any page type |
Core Instructions
Configuration
- Check for project-specific config at
.claude/project-config.md
- Read
project_id, project_name, project_url, locales, voice_and_tone, content_path
- Load project extension if it exists at
.claude/skills/creo-content/creo-content-{project_id}.md. This file contains project-specific brand voice, tone, target audience, JTBD, pain points, and i18n conventions. {project_id} comes from project-config.md. Always load it before doing work.
- If no config exists, use defaults or ask user
Pain Point Psychology
Customers buy solutions to problems. Identify:
- Functional pains: Time wasted, manual work, errors
- Emotional pains: Frustration, anxiety, embarrassment
- Financial pains: High costs, hidden fees, unpredictable pricing
- Social pains: Looking incompetent, missing deadlines
JTBD Framework
Every piece of content connects to a specific customer job:
When [SITUATION/CONTEXT],
I want to [MOTIVATION/ACTION],
So I can [EXPECTED OUTCOME/BENEFIT].
Content Creation Process
Step 1: Understand the Context
- Read the target page/section requirements
- Identify the primary audience segment
- Review pain points for that segment
- Check competitive messaging opportunities
Step 2: Apply JTBD Framework
- Who is the customer? (segment)
- What job are they trying to do?
- What pain points block them?
- How does the product solve this?
- What outcome do they achieve?
Step 3: Write with Pain-First Structure
Hero Section Formula:
[Pain Point / Problem Statement]
|
[Solution / Promise]
|
[Key Benefit / Outcome]
|
[CTA with Value]
Step 4: Output i18n-Ready JSON
{
"hero": {
"badge": "Category Label",
"headline": "Transform Your Workflow",
"subheadline": "Detailed value proposition addressing pain points.",
"cta": {
"primary": "Start Free",
"secondary": "See How It Works"
}
},
"features": {
"title": "Why Teams Choose Us",
"items": [
{
"icon": "globe",
"title": "Feature Name",
"description": "Benefit-focused description."
}
]
}
}
Copywriting Principles
Lead with Benefits, Not Features
| Feature |
Benefit |
| "Fast processing" |
"Save 10 hours every week" |
| "99.9% uptime" |
"Never miss a deadline" |
| "API access" |
"Integrate in minutes, not weeks" |
Use Power Words
- Action: Transform, Unlock, Accelerate, Simplify, Automate
- Emotion: Confident, Effortless, Powerful, Seamless
- Results: Instant, Accurate, Professional, Complete
Write Scannable Copy
- Headlines: 6-12 words max
- Subheadlines: One clear benefit
- Body: 2-3 sentences per paragraph max
- Bullets: Start with verbs, parallel structure
Page-Specific Guidelines
Homepage
- Goal: Capture attention, establish value, drive signup
- Primary CTA: Start Free Trial
- Secondary CTA: See Demo / Learn More
Feature Pages
- Goal: Deep dive into specific capability
- Structure: Problem, Solution, How It Works, Benefits, CTA
Pricing Page
- Goal: Convert visitors to paying customers
- Structure: Clear tiers, feature comparison, FAQ, guarantee
Use Case Pages
- Goal: Connect with specific audience segment
- Structure: Segment Pain, Our Solution, Success Story, Getting Started
Anti-Patterns to Avoid
Do not write:
- "Our product is the best in the market"
- "We use advanced AI technology"
- "Sign up now to get started"
- Generic benefits without specifics
Do write:
- "Save 10 hours every week on [task]"
- "95%+ accuracy, verified by independent testing"
- "Start free -- no credit card required"
- Specific outcomes and measurable results
Reference Files
Load these on demand for extended guidance:
| File |
Purpose |
references/pain-points-framework.md |
Customer pain analysis by segment |
references/voice-and-tone.md |
Brand voice guidelines |
Quality Gates
- Every piece of content must address a real customer pain point
- Headlines must lead with benefits, not features
- Content must be scannable (understand value in 5 seconds)
- CTA must be clear and action-oriented
- JSON structure must be valid and i18n-ready
- No jargon -- a non-technical person must understand it
- Competitive advantages must be highlighted
- JTBD alignment must be documented for each section
1---2name: creo-content3description: Marketing content strategist that creates compelling copy using JTBD framework, customer pain points, and competitive positioning. Generates i18n-ready JSON content for landing pages, feature pages, pricing pages, and marketing materials. Trigger keywords: marketing copy, content strategy, landing page copy, feature copy, pricing copy, JTBD content, i18n content.4---56# Marketing Content Strategy78Create compelling, conversion-focused marketing copy based on customer pain points, JTBD framework, and competitive advantages. Output is i18n-ready JSON for integration with internationalization systems.910## Commands1112| Command | Description |13|---------|-------------|14| `/creo content landing` | Generate landing page content |15| `/creo content feature` | Generate feature page content |16| `/creo content pricing` | Generate pricing page content |17| `/creo content <page-type>` | Generate content for any page type |1819## Core Instructions2021### Configuration22231. Check for project-specific config at `.claude/project-config.md`242. Read `project_id`, `project_name`, `project_url`, `locales`, `voice_and_tone`, `content_path`253. Load project extension if it exists at `.claude/skills/creo-content/creo-content-{project_id}.md`. This file contains project-specific brand voice, tone, target audience, JTBD, pain points, and i18n conventions. `{project_id}` comes from `project-config.md`. Always load it before doing work.264. If no config exists, use defaults or ask user2728### Pain Point Psychology2930Customers buy solutions to problems. Identify:31- **Functional pains**: Time wasted, manual work, errors32- **Emotional pains**: Frustration, anxiety, embarrassment33- **Financial pains**: High costs, hidden fees, unpredictable pricing34- **Social pains**: Looking incompetent, missing deadlines3536### JTBD Framework3738Every piece of content connects to a specific customer job:3940```41When [SITUATION/CONTEXT],42I want to [MOTIVATION/ACTION],43So I can [EXPECTED OUTCOME/BENEFIT].44```4546### Content Creation Process4748#### Step 1: Understand the Context491. Read the target page/section requirements502. Identify the primary audience segment513. Review pain points for that segment524. Check competitive messaging opportunities5354#### Step 2: Apply JTBD Framework55- Who is the customer? (segment)56- What job are they trying to do?57- What pain points block them?58- How does the product solve this?59- What outcome do they achieve?6061#### Step 3: Write with Pain-First Structure6263Hero Section Formula:64```65[Pain Point / Problem Statement]66 |67[Solution / Promise]68 |69[Key Benefit / Outcome]70 |71[CTA with Value]72```7374#### Step 4: Output i18n-Ready JSON7576```json77{78 "hero": {79 "badge": "Category Label",80 "headline": "Transform Your Workflow",81 "subheadline": "Detailed value proposition addressing pain points.",82 "cta": {83 "primary": "Start Free",84 "secondary": "See How It Works"85 }86 },87 "features": {88 "title": "Why Teams Choose Us",89 "items": [90 {91 "icon": "globe",92 "title": "Feature Name",93 "description": "Benefit-focused description."94 }95 ]96 }97}98```99100### Copywriting Principles101102#### Lead with Benefits, Not Features103| Feature | Benefit |104|---------|---------|105| "Fast processing" | "Save 10 hours every week" |106| "99.9% uptime" | "Never miss a deadline" |107| "API access" | "Integrate in minutes, not weeks" |108109#### Use Power Words110- Action: Transform, Unlock, Accelerate, Simplify, Automate111- Emotion: Confident, Effortless, Powerful, Seamless112- Results: Instant, Accurate, Professional, Complete113114#### Write Scannable Copy115- Headlines: 6-12 words max116- Subheadlines: One clear benefit117- Body: 2-3 sentences per paragraph max118- Bullets: Start with verbs, parallel structure119120### Page-Specific Guidelines121122#### Homepage123- Goal: Capture attention, establish value, drive signup124- Primary CTA: Start Free Trial125- Secondary CTA: See Demo / Learn More126127#### Feature Pages128- Goal: Deep dive into specific capability129- Structure: Problem, Solution, How It Works, Benefits, CTA130131#### Pricing Page132- Goal: Convert visitors to paying customers133- Structure: Clear tiers, feature comparison, FAQ, guarantee134135#### Use Case Pages136- Goal: Connect with specific audience segment137- Structure: Segment Pain, Our Solution, Success Story, Getting Started138139### Anti-Patterns to Avoid140141Do not write:142- "Our product is the best in the market"143- "We use advanced AI technology"144- "Sign up now to get started"145- Generic benefits without specifics146147Do write:148- "Save 10 hours every week on [task]"149- "95%+ accuracy, verified by independent testing"150- "Start free -- no credit card required"151- Specific outcomes and measurable results152153## Reference Files154155Load these on demand for extended guidance:156157| File | Purpose |158|------|---------|159| `references/pain-points-framework.md` | Customer pain analysis by segment |160| `references/voice-and-tone.md` | Brand voice guidelines |161162## Quality Gates163164- Every piece of content must address a real customer pain point165- Headlines must lead with benefits, not features166- Content must be scannable (understand value in 5 seconds)167- CTA must be clear and action-oriented168- JSON structure must be valid and i18n-ready169- No jargon -- a non-technical person must understand it170- Competitive advantages must be highlighted171- JTBD alignment must be documented for each section