/landing-page-copy

name: memstack-content-landing-page-copy
description: "Use this skill when the user says 'write landing page', 'landing page copy', 'sales page', 'hero section', 'conversion copy', or is creating persuasive short-form copy for a product or service landing page. Do NOT use for blog posts or email sequences."
version: 1.0.0
license: "Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt"

🎯 Landing Page Copy: Writing conversion-optimized page copy...

*Produces structured landing page copy blocks (hero, problem, solution, features, social proof, FAQ, CTA) ready to drop into any template or design.*

Activation

When this skill activates, output:

`🎯 Landing Page Copy, Gathering product and audience details...`

Then execute the protocol below.

| Context | Status | |---------|--------| | User says "write landing page" or "landing page copy" | ACTIVE | | User says "sales page" or "hero section" or "conversion copy" | ACTIVE | | Creating copy for a product, service, or signup page | ACTIVE | | Writing blog content (long-form, educational) | DORMANT: use blog-post | | Writing email copy | DORMANT: use email-sequence | | Designing the page layout (not writing copy) | DORMANT |

Anti-patterns

| Trap | Reality Check | |------|---------------| | "Describe all the features" | Features tell. Benefits sell. Lead with what the customer gets, not what the product does. | | "Make the headline clever" | Clever headlines confuse. Clear headlines convert. Clarity beats creativity every time. | | "Everyone is our audience" | Speaking to everyone means connecting with no one. Pick one persona and write to them. | | "Long copy won't be read" | Long copy outperforms short copy when every sentence earns the next. Cut filler, not length. | | "We don't need social proof yet" | No testimonials? Use stats, logos, case study snippets, or "built by" credibility. Something is always better than nothing. |

Protocol

Step 1: Gather Product Details

If the user hasn't provided details, ask:

> I need a few details for the landing page: > 1. **Product/service name**: what are we selling? > 2. **Target audience**: who is the ideal customer? (role, pain point, situation) > 3. **Key benefit**: what's the #1 thing they get? (in their words, not yours) > 4. **Price point**: free, freemium, one-time, subscription? (affects urgency strategy) > 5. **CTA goal**: what's the primary action? (sign up, buy, book a call, download) > 6. **Existing copy or brand voice**: any tone/style to match?

Step 2: Write Hero Section

The hero section determines whether visitors stay or leave. Every word earns its place.

## Hero Section

### Headline (10 words max)
[Clear statement of the primary benefit: what they get]

### Subheadline (20 words max)
[Specificity: who it's for, how it works, what makes it different]

### Primary CTA Button
[Action verb + outcome: "Start Free Trial" / "Get Your Report" / "Book a Demo"]

### Supporting text (optional, below CTA)
[Reduce friction: "No credit card required" / "Free for 14 days" / "Setup in 2 minutes"]

**Headline formulas:**

| Formula | Example | |---------|---------| | [Outcome] Without [Pain] | "Ship Faster Without Breaking Production" | | [Outcome] for [Audience] | "Beautiful Dashboards for Data Teams" | | The [Category] That [Difference] | "The CRM That Writes Itself" | | Stop [Pain]. Start [Benefit]. | "Stop Guessing. Start Knowing." | | [Number] [Outcome] in [Timeframe] | "10x Revenue in 90 Days" |

**Headline rules:**

• No jargon the visitor wouldn't say out loud
• Specific beats vague ("Save 10 hours/week" beats "Save time")
• One benefit only, trying to say everything says nothing
• If you can add "so what?" and it still makes sense, the headline is too vague

**CTA button rules:**

• Action verb first ("Start," "Get," "Try," "Download", never "Submit" or "Click Here")
• 2-5 words max
• State the outcome, not the action ("Get My Free Report" not "Download PDF")
• One primary CTA per section: don't split attention

Step 3: Problem / Agitation Section

Make the reader feel their problem before presenting the solution:

## Problem Section

### Section headline
[Name the pain directly: "Tired of [problem]?" / "You know the feeling..."]

### Pain points (3-4 bullet points)
- [Specific frustration they experience daily]
- [Consequence of not solving this problem]
- [The thing they've tried that didn't work]
- [The emotional cost: stress, wasted time, missed opportunities]

### Agitation paragraph
[1-2 sentences amplifying the stakes: what happens if they do nothing?
Paint the future they don't want.]

**Problem section rules:**

• Use the reader's own language (words from reviews, support tickets, forums)
• Be specific, "You spend 3 hours every Monday compiling reports" not "Reports take too long"
• Don't insult the reader or their current tools: empathize with their situation
• The problem section ends with the reader thinking "Yes, that's exactly my problem"

Step 4: Solution Section

Transition from pain to relief. This is where your product enters:

## Solution Section

### Transition line
[Bridge from problem to solution: "What if you could..." / "That's why we built..." / "Imagine instead..."]

### Product introduction (2-3 sentences)
[Product name] [does what] for [whom]. [How it solves the problem stated above].
[One sentence about the approach or key differentiator.]

### How it works (3 steps)
1. **[Action verb]**: [Simple first step the user takes]
2. **[Action verb]**: [What happens next / the product's magic moment]
3. **[Action verb]**: [The outcome they get]

### Visual suggestion
[Screenshot, demo GIF, or product illustration showing the solution in action]

**Solution section rules:**

• The "how it works" should be 3 steps max: complexity kills conversion
• Each step starts with an action verb
• Show, don't tell, include a visual of the product
• Connect back to the problem