Run any Skill in Manus with one click

landing-page-copywriter

Stars5

Forks0

UpdatedJuly 2, 2026 at 17:22

Write landing page copy that converts. Hero + 3 value props + social proof + objections + CTA. Anchored on validated user language.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hamza-ali-shahjahan

hamza-ali-shahjahan/hamzaish

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Technical WritersArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3042

SKILL.md

readonly

name	landing-page-copywriter
description	Write landing page copy that converts. Hero + 3 value props + social proof + objections + CTA. Anchored on validated user language.
model_tier	sonnet

Landing Page Copywriter

When you activate

User asks: "write the landing page for X", "redo the hero for Y", "the conversion on Z is bad"

What you produce

Saved to products/<name>/launch/landing-copy.md:

## Landing — <product>

### Above the fold
**Headline (≤10 words):** <user's words, not yours>
**Sub-headline (≤25 words):** <the differentiator + the outcome>
**Primary CTA:** <action verb + outcome> (e.g., "Start a free 5-min audit")
**Secondary CTA:** <lower-commitment alt> (e.g., "See a sample report")
**Visual:** <one sentence describing the hero visual — screenshot, video, animation, product GIF>

### Section 2: Problem (the pain)
3 bullets in user's voice — pulled from interview synthesis. Each is one sentence + one specific consequence.

### Section 3: Solution (3 value props)
Three benefits, each: <verb-led headline> + <2 sentences> + <visual / screenshot>

### Section 4: How it works (3 steps)
1. <step> (one verb + one noun)
2. <step>
3. <step>

### Section 5: Social proof
- Founder quote / waitlist counter / press logos / customer logos (whichever is available)

### Section 6: Objection handling (FAQ)
The 5 questions that lose the deal — answered tightly.

### Section 7: Final CTA
Restate the primary CTA + add a guarantee or risk-reduction (free trial, money-back, no credit card required, etc.)

Protocol

Read the product's interviews/synthesis-*.md — pull verbatim quotes for the headline and pain bullets.
Read the product's brand.md for voice and positioning.
Read factory/playbooks/launch-stage/seo-content-strategy.md for headline → SEO interaction.
Draft headlines in 3 voices: practical, aspirational, irreverent. Pick the one that matches brand.md voice.
The "How it works" section: 3 steps max. If it takes 5 steps to explain, your product is too complex for the homepage.
The FAQ section: write 5 real objections from interviews, not generic ones.
Output the copy as markdown ready to drop into the Next.js landing template at templates/landing-page-template/.

Copy rules

Headlines are short. Cut every word that doesn't earn its space.
Use specific numbers when you have them ("Save 4 hours/week" > "Save time")
Use the customer's words, not yours. If interviews said "ungovernable spreadsheet," use "ungovernable spreadsheet."
Avoid every word on this list: leverage, unleash, supercharge, robust, scalable, seamless, intelligent, powerful, revolutionary.

Contract (handoff)

Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:

Preconditions (from brand-story-builder + interview-synthesizer): launch/brand.md exists (voice + positioning are its API); interview synthesis exists for the problem bullets and objections/FAQ.
On precondition gap: missing brand.md → run brand-story-builder first (copy written before positioning gets rewritten after it — do it once). Missing synthesis → write the objections section anyway but mark each as assumption, needs validation — never present invented objections as customer language.
Produces: products/<name>/launch/landing-copy.md in the format above.
Shape: guaranteed sections — Above the fold / Problem / Solution (3 props) / How it works (≤3 steps) / Social proof / Objections FAQ / Final CTA.
Postconditions: headline and problem bullets use words that appear in interview quotes where they exist; zero banned buzzwords; every CTA is verb + outcome.

Sources

factory/playbooks/launch-stage/seo-content-strategy.md
factory/playbooks/launch-stage/first-100-customers.md
The product's interviews/synthesis-*.md

What you don't do

Don't invent customer quotes
Don't write more than 7 sections — landing pages should fit in two scrolls
Don't use the buzzwords list above

More from this repository

same repository

feature-slicing

hamza-ali-shahjahan/hamzaish

Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.

2026-07-215

go-live

hamza-ali-shahjahan/hamzaish

Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.

2026-07-215

spec-driven-development

hamza-ali-shahjahan/hamzaish

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

2026-07-215

factory-launch

hamza-ali-shahjahan/hamzaish

Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.

2026-07-185

scaffold

hamza-ali-shahjahan/hamzaish

One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.

2026-07-145

planning-and-task-breakdown

hamza-ali-shahjahan/hamzaish

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

2026-07-025

Landing Page Copywriter

When you activate

User asks: "write the landing page for X", "redo the hero for Y", "the conversion on Z is bad"

What you produce

Saved to products/<name>/launch/landing-copy.md:

## Landing — <product> ### Above the fold **Headline (≤10 words):** <user's words, not yours> **Sub-headline (≤25 words):** <the differentiator + the outcome> **Primary CTA:** <action verb + outcome> (e.g., "Start a free 5-min audit") **Secondary CTA:** <lower-commitment alt> (e.g., "See a sample report") **Visual:** <one sentence describing the hero visual — screenshot, video, animation, product GIF> ### Section 2: Problem (the pain) 3 bullets in user's voice — pulled from interview synthesis. Each is one sentence + one specific consequence. ### Section 3: Solution (3 value props) Three benefits, each: <verb-led headline> + <2 sentences> + <visual / screenshot> ### Section 4: How it works (3 steps) 1. <step> (one verb + one noun) 2. <step> 3. <step> ### Section 5: Social proof - Founder quote / waitlist counter / press logos / customer logos (whichever is available) ### Section 6: Objection handling (FAQ) The 5 questions that lose the deal — answered tightly. ### Section 7: Final CTA Restate the primary CTA + add a guarantee or risk-reduction (free trial, money-back, no credit card required, etc.)

Protocol

Read the product's interviews/synthesis-*.md — pull verbatim quotes for the headline and pain bullets.

Read the product's brand.md for voice and positioning.

Read factory/playbooks/launch-stage/seo-content-strategy.md for headline → SEO interaction.

Draft headlines in 3 voices: practical, aspirational, irreverent. Pick the one that matches brand.md voice.

The "How it works" section: 3 steps max. If it takes 5 steps to explain, your product is too complex for the homepage.

The FAQ section: write 5 real objections from interviews, not generic ones.

Output the copy as markdown ready to drop into the Next.js landing template at templates/landing-page-template/.

Copy rules

Headlines are short. Cut every word that doesn't earn its space.

Use specific numbers when you have them ("Save 4 hours/week" > "Save time")

Use the customer's words, not yours. If interviews said "ungovernable spreadsheet," use "ungovernable spreadsheet."

Avoid every word on this list: leverage, unleash, supercharge, robust, scalable, seamless, intelligent, powerful, revolutionary.

Contract (handoff)

Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:

Preconditions (from brand-story-builder + interview-synthesizer): launch/brand.md exists (voice + positioning are its API); interview synthesis exists for the problem bullets and objections/FAQ.

On precondition gap: missing brand.md → run brand-story-builder first (copy written before positioning gets rewritten after it — do it once). Missing synthesis → write the objections section anyway but mark each as assumption, needs validation — never present invented objections as customer language.

Produces: products/<name>/launch/landing-copy.md in the format above.

Shape: guaranteed sections — Above the fold / Problem / Solution (3 props) / How it works (≤3 steps) / Social proof / Objections FAQ / Final CTA.

Postconditions: headline and problem bullets use words that appear in interview quotes where they exist; zero banned buzzwords; every CTA is verb + outcome.

Sources

factory/playbooks/launch-stage/seo-content-strategy.md

factory/playbooks/launch-stage/first-100-customers.md

The product's interviews/synthesis-*.md

What you don't do

Don't invent customer quotes

Don't write more than 7 sections — landing pages should fit in two scrolls

Don't use the buzzwords list above