afrexai-conversion-copywriting
Write high-converting copy for any surface — landing pages, emails, ads, sales pages, product descriptions, CTAs, video scripts, and more. Complete conversion copywriting system with research methodology, 12 proven frameworks, swipe-file templates, scoring rubrics, and A/B testing protocols. Use when you need to write or review any copy meant to drive action.
What this skill does
# Conversion Copywriting Engine
> Copy is salesmanship in print. This isn't about writing — it's about selling. Every word earns its place or gets cut.
## Quick Health Check
Rate the copy 1-5 on each dimension. Score < 24 = rewrite needed:
| # | Dimension | Question |
|---|-----------|----------|
| 1 | Clarity | Can a 12-year-old understand the offer in 5 seconds? |
| 2 | Specificity | Are there numbers, timeframes, and concrete outcomes? |
| 3 | Desire | Does the reader WANT the outcome described? |
| 4 | Proof | Is there evidence (testimonials, data, logos, case studies)? |
| 5 | Urgency | Is there a reason to act NOW vs later? |
| 6 | Friction | Are objections addressed before they arise? |
| 7 | Voice | Does it sound like a human, not a corporation? |
| 8 | CTA | Is the next step crystal clear and low-risk? |
**Score: /40** — Below 32 = significant opportunity. Below 24 = copy is actively losing money.
---
## Phase 1: Research Before Writing
Never write a single word until you complete this. Bad research = bad copy, no matter how clever.
### 1.1 Voice of Customer (VoC) Mining
The goal: steal your customer's EXACT words and mirror them back.
**Sources (ranked by value):**
| Source | What to Extract | Where to Find |
|--------|----------------|---------------|
| Support tickets | Pain language, frustration words | Helpdesk, Intercom, Zendesk |
| Sales call recordings | Objections, "I wish...", buying triggers | Gong, call notes |
| Review sites | Praise patterns, complaint patterns | G2, Capterra, Trustpilot, Amazon |
| Reddit/forums | Unfiltered problems, slang, emotional language | r/[industry], Quora, niche forums |
| Competitor reviews | What competitors fail at (your opportunity) | G2, App Store, Amazon |
| Survey responses | Direct answers to "why did you buy/not buy?" | Typeform, post-purchase surveys |
| Social comments | Reaction language, share triggers | Twitter replies, LinkedIn comments |
**VoC Extraction Template:**
```yaml
voC_research:
product: "[Product name]"
date: "YYYY-MM-DD"
pain_statements: # Exact quotes about the problem
- quote: "I spend 3 hours every morning just reconciling invoices"
source: "G2 review - AccountingSoft competitor"
frequency: "high" # How often this sentiment appears
- quote: ""
source: ""
frequency: ""
desire_statements: # What they WANT (outcome language)
- quote: "I just want to click one button and have it done"
source: "Reddit r/smallbusiness"
frequency: "medium"
- quote: ""
source: ""
frequency: ""
objection_statements: # Why they hesitate
- quote: "Every tool like this requires a PhD to set up"
source: "Support ticket"
frequency: "high"
- quote: ""
source: ""
frequency: ""
trigger_events: # What made them start looking
- "Hired 5th employee and spreadsheets broke"
- "Missed a tax deadline"
- ""
words_they_use: # Industry/audience vocabulary
- "reconciliation" not "financial harmonization"
- "setup" not "onboarding flow"
- ""
competitors_they_mention: []
buying_criteria: # What matters most (ranked)
- "Easy to set up (< 1 hour)"
- "Integrates with QuickBooks"
- ""
```
### 1.2 Awareness Levels (Eugene Schwartz)
Every piece of copy must match the reader's awareness level. Writing "Buy now!" to someone who doesn't know they have a problem = wasted words.
| Level | They Know... | Your Job | Lead With |
|-------|-------------|----------|-----------|
| **Unaware** | Nothing about the problem | Educate about the pain | Story, shocking stat, question |
| **Problem-Aware** | They have a problem | Agitate the pain, introduce solution category | "Tired of X? Here's why..." |
| **Solution-Aware** | Solutions exist | Differentiate YOUR solution | "Unlike other tools, we..." |
| **Product-Aware** | Your product exists | Overcome objections, prove value | Social proof, comparison, demo |
| **Most Aware** | Your product, ready to buy | Remove final friction | Deal, guarantee, urgency |
**Rule:** The less aware they are, the longer the copy needs to be. Unaware = long-form education. Most Aware = short CTA + offer.
### 1.3 One Reader, One Offer, One Action
Before writing, fill this in:
```yaml
copy_brief:
surface: "" # Landing page, email, ad, sales page, etc.
one_reader: "" # Specific person (not "small businesses" — "Sarah, ops manager at 50-person agency")
awareness_level: "" # Unaware / Problem / Solution / Product / Most Aware
one_offer: "" # What exactly are you offering?
one_action: "" # What exactly should they DO?
primary_emotion: "" # Fear, desire, curiosity, frustration, hope
proof_available: [] # Testimonials, case studies, data points you can use
objections_to_address: [] # Top 3 reasons they'd say no
word_count_target: "" # Constraint forces clarity
```
---
## Phase 2: Headline Writing
The headline does 80% of the work. If the headline fails, nothing else matters.
### 2.1 Headline Formulas (12 Proven Patterns)
| # | Formula | Example |
|---|---------|---------|
| 1 | **[Number] Ways to [Desired Outcome] Without [Pain]** | "7 Ways to Cut Hiring Time Without Lowering Standards" |
| 2 | **How [Specific Person] [Achieved Result] in [Timeframe]** | "How a 3-Person Agency Landed $240K in Clients in 90 Days" |
| 3 | **Stop [Bad Thing]. Start [Good Thing].** | "Stop Guessing at Pricing. Start Charging What You're Worth." |
| 4 | **The [Adjective] Way to [Outcome]** | "The Lazy Way to Write Emails That Get Replies" |
| 5 | **[Outcome] in [Timeframe] — or [Bold Guarantee]** | "Double Your Pipeline in 30 Days — or We Work Free Until You Do" |
| 6 | **Why [Counterintuitive Claim]** | "Why Your Best Salesperson Is Costing You Revenue" |
| 7 | **[Pain Statement] → [Outcome Statement]** | "From 60-Hour Weeks → Automated Operations in 14 Days" |
| 8 | **What [Respected Group] Knows About [Topic] That You Don't** | "What Top 1% of SaaS Founders Know About Pricing" |
| 9 | **Are You Making These [Number] [Mistake Type] Mistakes?** | "Are You Making These 5 Cold Email Mistakes?" |
| 10 | **[Big Number/Stat] + Implication** | "83% of Proposals Lose on Price. Here's How to Win on Value." |
| 11 | **The [Framework/Secret/Method] Behind [Impressive Result]** | "The 3-Step Method Behind $50M in Closed Deals" |
| 12 | **[Direct Command] + [Specific Benefit]** | "Cut Your Client Reporting Time by 80% This Week" |
### 2.2 Headline Quality Test
Score each headline candidate 0-2 per criterion:
| Criterion | 0 | 1 | 2 |
|-----------|---|---|---|
| **Specific** | Vague/generic | Somewhat specific | Has numbers, timeframes, or concrete nouns |
| **Benefit-driven** | Feature-focused | Implied benefit | Explicit outcome the reader wants |
| **Curiosity gap** | No reason to read on | Mild interest | "I NEED to know more" |
| **Believable** | Sounds like hype | Plausible | Backed by specificity or proof |
| **Emotional** | Flat/corporate | Slightly engaging | Hits fear, desire, curiosity, or frustration |
**Score: /10** — Ship at 7+. Below 5 = rewrite.
### 2.3 Subheadline Rules
The subheadline expands on the headline promise. It should:
- Add specificity the headline couldn't fit
- Address the reader directly ("you")
- Lower the perceived effort/risk
- Create a "nodding" effect (reader thinks "yes, that's me")
**Pattern:** `[Expand on headline promise] + [For whom] + [Without the main objection]`
Example: Headline: "Double Your Pipeline in 30 Days"
Subheadline: "The AI-powered outreach system that books qualified calls for B2B founders — without cold calling or hiring SDRs."
---
## Phase 3: Copy Frameworks (The Arsenal)
### 3.1 Core Frameworks
**AIDA — Attention, Interest, Desire, Action**
Best for: Landing pages, sales pages, long-form emails
```
ATTENTION: Hook with the biggest pain or boldest promise
INTEREST: "Here's why this matters to YOU specifically..."
DESIRE: Paint the after-state. MaRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".