Load Context First

Before executing this skill, read the following files from the project folder if they exist:

1. USER.md — who the user is, how they think, how they work
2. BUSINESS.md — their business, products, positioning, brand voice, content strategy
3. ICP.md — their ideal customer, their language, their fears, what makes them buy
4. Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
5. Any additional context provided by the user in this session

Use all context silently. Do not reference or summarize files unless asked.

Sales Page Writer

Purpose: Write complete, conversion-optimized sales page copy for digital products and services. The output follows proven direct-response structure while maintaining the user's authentic voice.

When to Activate

Use this skill when:

• User needs sales page or landing page copy
• User mentions "sales page", "product page", or "conversion copy"
• User is launching a product and needs the page written
• User wants to improve an existing sales page

Required Information

Gather from context files or ask:

• Product name and description
• Price (and payment plans if any)
• Target audience (who is this for?)
• The problem it solves (specific pain points)
• The transformation (where they are now → where they'll be)
• What's included (features, modules, deliverables)
• Testimonials (if available)
• Guarantee (if offered)
• Bonuses (if any)

Sales Page Structure

Section 1: Hero (Above the Fold)

Headline: Targets the dream outcome. Specific, not vague.

• Formula: [Desired Outcome] + [Timeframe or Method] + [For Whom]
• Example: "Build a Content System That Produces 30 Pieces a Week — Without Hiring Anyone"

Subheadline: Expands on the headline. Adds context or removes an objection.

CTA Button: Clear action text. Not "Submit" — use "Get Instant Access", "Join Now", "Start Building Today."

Social proof line: (optional) "Join 500+ [type of people] who already [result]"

Section 2: Pain / Problem (200-300 words)

Describe the problem the buyer is experiencing. Use their language from ICP.md.

Rules:

• Write in second person ("You've tried..." / "You're tired of...")
• Be specific about the pain (not "things are hard")
• Include 3-5 specific symptoms they'll recognize
• Make them feel understood, not attacked

Section 3: Agitation (100-200 words)

Amplify the cost of NOT solving this problem. What happens if they keep doing what they're doing?

Include:

• Time wasted
• Money left on the table
• Opportunity cost
• Emotional toll

Rule: Don't fear-monger. State the real consequences honestly.

Section 4: Solution Introduction (150-250 words)

Introduce the product as the bridge between their problem and their desired outcome.

Structure:

• "What if..." or "Imagine..." (paint the after)
• Introduce the product by name
• One sentence on what it is
• One sentence on who it's for
• One sentence on what makes it different

Section 5: Features → Benefits (300-500 words)

List every feature/deliverable and translate it into a benefit.

Format for each:

### [Feature Name]
[What it is — 1 sentence]
**What this means for you:** [The benefit — the outcome they care about]

Rule: Features tell, benefits sell. "12 video modules" = feature. "A step-by-step system you can implement in a weekend" = benefit.

Section 6: Social Proof (Variable)

If testimonials exist: Include 3-5 formatted testimonials with name, role, and specific result.

If no testimonials yet: Add placeholder sections:

[TESTIMONIAL PLACEHOLDER: Add customer testimonial focusing on {specific benefit}]

Formats that work:

• Pull quote with attribution
• Before → After transformation
• "I was skeptical but..." format

Section 7: Objection Handling / FAQ (8-10 questions)

Address the most common objections disguised as helpful Q&A.

Must-include objections:

1. "Is this right for my [situation]?" → Yes, because...
2. "What if I don't have time?" → Here's how long it actually takes...
3. "How is this different from [alternative]?" → The key difference is...
4. "What if it doesn't work for me?" → [Guarantee] + [support structure]
5. "Can I really get [result]?" → Here's how others have...

Format:

**Q: [Question in the buyer's voice]**
A: [Direct, honest answer — 2-4 sentences]

Section 8: Pricing + Value Stack (Variable)

Value stack table:

Payment plans (if applicable):

• One payment of $[X]
• [Y] payments of $[Z]

Section 9: Guarantee (50-100 words)

State the guarantee clearly and confidently.

Patterns:

• "30-day money-back guarantee. Try it risk-free."
• "If you don't [specific result] within [timeframe], [refund terms]."
• "No questions asked" OR "with [reasonable condition]"

Section 10: Final CTA (50-100 words)

Restate the transformation. Restate the price. Clear button.

Structure:

• One sentence about the transformation
• Price reminder
• CTA button
• "Still have questions? [Contact link]"

Output Format

# Sales Page: [Product Name]

---

## [HERO]

### [Headline]
[Subheadline]

[CTA Button: "Button Text"]

[Social proof line]

---

## [PAIN]
[Pain section copy]

---

## [AGITATION]
[Agitation copy]

---

## [SOLUTION]
[Solution introduction]

---

## [FEATURES → BENEFITS]
[Feature/benefit sections]

---

## [SOCIAL PROOF]
[Testimonials or placeholders]

---

## [FAQ]
[8-10 Q&A pairs]

---

## [PRICING]
[Value stack + pricing]

---

## [GUARANTEE]
[Guarantee statement]

---

## [FINAL CTA]
[Closing copy + button]

Quality Checklist

• Headline targets dream outcome (not product name)
• Pain section uses ICP's actual language
• Every feature has a corresponding benefit
• FAQ addresses real objections (not softballs)
• Value stack shows clear price-to-value gap
• CTA buttons use action-oriented language
• Guarantee is stated clearly
• Voice matches context profiles
• No fabricated testimonials or results
• Copy flows naturally from problem → solution → proof → action