borghei/landing-page-generator
> Generate high-converting landing pages with page structure, copy frameworks (PAS, AIDA, BAB), CTA strategy, SEO meta, and Core Web Vitals optimization. Use when creating landing pages, campaign pages, lead capture pages, or conversion pages.
npx skills add https://github.com/borghei/Claude-Skills --skill landing-page-generator
Design and build high-converting landing pages using proven copy frameworks, section patterns, and conversion optimization techniques.
landing page, landing page design, conversion optimization, lead capture page, campaign page, marketing page, hero section, CTA strategy, landing page copy, landing page generator, promo page, conversion page, lead gen page, single-page site, landing page template, A/B testing, page layout, above the fold, social proof, pricing table, FAQ section, testimonial block
Before generating the page, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
## Landing Page Brief
- Product/Service: [Name]
- Value proposition: [One sentence]
- Target audience: [Who and what they need]
- Key pain point: [Primary problem you solve]
- Key benefit: [Primary outcome they get]
- Offer: [What you are offering — trial, demo, download, purchase]
- Traffic source: [Where visitors come from — ads, email, organic]
- Design style: [dark-saas / clean-minimal / bold-startup / enterprise]
- Copy framework: [PAS / AIDA / BAB]
Step 1: Define the Single Goal
Every landing page has one purpose and one CTA. Define it before anything else:
Step 2: Select Copy Framework
| Framework | Best When | Audience Awareness Level |
|-----------|-----------|------------------------|
| PAS (Problem > Agitate > Solve) | Audience knows the problem | Problem-aware |
| AIDA (Attention > Interest > Desire > Action) | Audience needs education | Unaware to problem-aware |
| BAB (Before > After > Bridge) | Audience wants transformation | Solution-aware |
Step 3: Build Sections in Order
| Order | Section | Purpose |
|-------|---------|---------|
| 1 | Hero | Communicate value in 5 seconds |
| 2 | Social proof bar | Build instant credibility |
| 3 | Problem statement | Show you understand their pain |
| 4 | Solution / Benefits | Present your answer |
| 5 | How it works | Reduce perceived complexity |
| 6 | Features with benefits | Detail what they get |
| 7 | Testimonials | Proof from real customers |
| 8 | Pricing (if applicable) | Help them decide |
| 9 | FAQ | Handle objections |
| 10 | Final CTA | Repeat the ask with risk reversal |
Step 4: Write Copy Per Section
Use the section-specific guidelines in the Page Section Library below.
Step 5: Optimize for Conversion
Run the Conversion Optimization Checklist before launching.
For ad campaigns, email campaigns, or launch events:
Step 1: Message Match
The landing page headline MUST match the ad/email that drives traffic:
Step 2: Single Message Focus
Remove all navigation, sidebar links, and secondary CTAs:
Step 3: Traffic Source Adaptation
| Traffic Source | Page Adaptation |
|---------------|----------------|
| Paid search (Google) | Lead with the searched keyword in H1 |
| Paid social (Meta, LinkedIn) | Lead with the ad's hook/benefit |
| Email campaign | Lead with the email's promise |
| Organic search | Lead with the comprehensive answer |
| Referral/partner | Lead with the referrer's context |
The most important section. Must communicate value in 5 seconds.
Components:
Hero Variants:
| Variant | Layout | Best For |
|---------|--------|----------|
| Centered | Text centered, CTA below, visual below | Simple offers, clear value props |
| Split | Text left, visual right (or vice versa) | Product with strong visual/screenshot |
| Video background | Text overlay on ambient video | Brand-heavy, awareness pages |
| Minimal | Headline + CTA only, no visual | High-intent traffic, direct offers |
| Social proof hero | Testimonial as the headline | Strong customer story to lead with |
Hero Copy Guidelines:
Make the reader feel understood before pitching anything.
Structure:
Connect your product to the outcomes they want.
Structure:
Reduce perceived complexity to 3-4 simple steps.
Structure:
Rules:
Types ranked by conversion impact:
| Type | Impact | Example |
|------|--------|---------|
| Named testimonial with metrics | Highest | "Reduced churn by 23% in 90 days" — Sarah Chen, VP Marketing |
| Customer logos | High | Row of recognizable brand logos |
| Aggregate metrics | High | "2,847 teams, 40+ countries, 4.8/5 rating" |
| Star ratings / review scores | Medium | "4.8 out of 5 on G2 (500+ reviews)" |
| Case study link | Medium | "See how [Company] achieved [result]" |
| Generic testimonial | Low | "Great product!" — John D. |
Guidelines:
Guidelines:
Common FAQ questions to include:
Structure:
| Section | PAS Element | Copy Approach |
|---------|------------|---------------|
| Hero headline | Problem | Name the pain directly |
| Problem section | Agitate | Show consequences of inaction |
| Solution section | Solve | Introduce product as the answer |
| CTA | Solve | Clear action to access the solution |
Example:
| Section | AIDA Element | Copy Approach |
|---------|-------------|---------------|
| Hero headline | Attention | Bold, attention-grabbing statement |
| Benefits section | Interest | Expand with relevant details and benefits |
| Social proof | Desire | Show proof and paint the transformation |
| CTA | Action | Clear, compelling call to action |
| Section | BAB Element | Copy Approach |
|---------|------------|---------------|
| Hero + Problem | Before | Current painful state |
| Solution + Benefits | After | Desired future state |
| How it works | Bridge | How the product gets them there |
| Style | Visual Tone | Best For |
|-------|-----------|----------|
| Dark SaaS | Dark backgrounds, vibrant accents, gradient effects | Developer tools, technical products, modern SaaS |
| Clean Minimal | White backgrounds, subtle borders, clean typography | Professional services, healthcare, education |
| Bold Startup | Large typography, bright colors, dynamic layouts | Consumer products, startups, creative tools |
| Enterprise | Muted tones, structured layouts, conservative design | B2B enterprise, finance, government |
| Position | Purpose | Copy Approach |
|----------|---------|---------------|
| Hero | Primary conversion point | Action + benefit: "Start my free trial" |
| After benefits | Capture interest momentum | Reinforce: "See it in action" |
| After social proof | Capitalize on trust | Social: "Join 2,847 teams" |
| Page footer | Final catch | Urgency: "Start today — free for 14 days" |
[Action Verb] + [What They Get]
Below the button, reduce friction:
| Metric | Target | How to Achieve |
|--------|--------|---------------|
| Largest Contentful Paint (LCP) | Under 2.5 seconds | Optimize hero image, use modern formats (WebP/AVIF) |
| Cumulative Layout Shift (CLS) | Under 0.1 | Set explicit dimensions on all images and embeds |
| First Input Delay (FID) | Under 100ms | Defer non-critical JavaScript |
| Time to First Byte (TTFB) | Under 600ms | Use CDN, server-side rendering, or static generation |
| Total page weight | Under 1MB | Compress images, minimize JavaScript bundles |
## A/B Test: [Name]
- Page: [URL]
- Hypothesis: [If we change X, then Y improves because Z]
- Control: [Current version]
- Variant: [Changed version]
- Primary metric: [Conversion rate / Click rate / Signup rate]
- Duration: [Start - End]
- Traffic per variant: [Number]
- Result: [Winner + lift + confidence]
- Learning: [What we apply going forward]
10. Risk reversal near every CTA — "No credit card required," "Money-back guarantee," "Cancel anytime." Remove the last objection at the moment of decision.
| Symptom | Likely Cause | Fix |
|---------|-------------|-----|
| High bounce rate from paid traffic | Headline doesn't match the ad | Ensure exact message match between ad copy and landing page H1. |
| CTA below fold on mobile | Hero section too tall or CTA not prioritized | Test on 375px viewport. CTA must be visible without scrolling. |
| Good traffic but zero conversions | Conversion tracking broken | Verify pixel fires on thank-you page. Test with a real conversion. |
| Slow page load (>3s mobile) | Unoptimized images, heavy JS | Run page_speed_estimator.py. Convert images to WebP, defer non-critical JS. |
| Form submissions but no leads in CRM | Form-to-CRM integration broken | Test form submission end-to-end. Check webhook/API connection. |
| Multiple CTAs confusing visitors | Too many conversion paths | Single goal per landing page. All CTAs drive the same action. |
| Low conversion despite good copy | No social proof or risk reversal | Run conversion_checklist.py. Add testimonials and "no credit card" near CTAs. |
In Scope: Landing page structure, section patterns, copy framework application, conversion optimization, CTA strategy, SEO meta tags, A/B testing framework, design style guidance.
Out of Scope: Page copy writing (use copywriting), paid ad campaigns driving traffic (use paid-ads), CMS/website builder administration, analytics platform setup.
Limitations: Conversion benchmarks vary significantly by industry, traffic source, and offer type. The 6.6% median is across all industries; SaaS trials may see 10-25% while e-commerce may see 2-3%.
scripts/page_speed_estimator.py)Estimates Core Web Vitals from HTML source: LCP, CLS risk, script/image analysis, and conversion impact.
python scripts/page_speed_estimator.py page.html
python scripts/page_speed_estimator.py page.html --json
scripts/cta_analyzer.py)Analyzes CTA placement, copy strength, friction level, and consistency across the landing page.
python scripts/cta_analyzer.py page.html
python scripts/cta_analyzer.py page.html --json
scripts/conversion_checklist.py)Runs a comprehensive 20+ point conversion optimization audit against 2025-2026 best practices and benchmarks.
python scripts/conversion_checklist.py page.html
python scripts/conversion_checklist.py page.html --json
Take borghei/landing-page-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.