landing-page-generator
When the user wants to create, optimize, or audit campaign landing pages for paid ads, email, or other traffic. Also use when the user mentions "landing page," "PPC landing page," "SEM landing page," "conversion page," "campaign page," "lead capture page," "landing page optimization," "LP conversion," "single-page funnel," or "squeeze page." Not for the main site homepage; use homepage-generator.
What this skill does
# Pages: Landing Page
Guides campaign landing page structure, conversion flow, and optimization. **Primary use**: **Paid ads (PPC/SEM)** — landing pages are typically built to receive paid traffic; ad-to-page alignment is critical for conversion. See **paid-ads-strategy** for when to use paid ads and ad-to-page alignment principles. Also applies to affiliate signup, product launch, lead capture, webinar registration, and other single-goal conversion pages. **Scale**: When building many landing pages (city-specific, product-specific, integration-specific), use **programmatic-seo** (template + data) and **template-page-generator** for template design. Differs from homepage (multi-purpose) and product pages (catalog).
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
## Paid Ads: LP Requirements
When LP receives paid traffic: ad promise on page immediately; mobile-first (CTA above fold, fast load); minimal form (fewer fields); trust above fold. See **paid-ads-strategy** for full ad-to-page alignment and Quality Score.
## Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and value proposition.
Identify:
1. **Page goal**: Signup, purchase, lead capture, webinar, download
2. **Traffic source**: Paid ads, email, affiliate, organic
3. **Audience**: Cold vs warm; segment if known
## Landing Page Structure (5-Step Flow)
| Step | Purpose | Elements |
|------|---------|----------|
| **1. Stop the scroll** | Capture attention in ~2.6 seconds | Headline, subheadline, hero image or video |
| **2. Earn trust** | Social proof before the ask | Logos, testimonials, ratings, customer count |
| **3. Explain value** | Benefits, features, use cases | Clear copy; who it's for, what it does |
| **4. Remove doubt** | Objection handling | FAQ, guarantees, comparison |
| **5. Make the ask** | Single primary CTA | One clear action; repeat at logical points |
Every element should serve one of these five functions. Pages with multiple competing offers get ~266% fewer leads.
## Headline Formula
**[Who it's for]** + **[Specific outcome]** + **[Time/qualifier]**
- **Avoid**: Abstract promises ("Unlock your potential," "Transform your business")
- **Prefer**: Concrete ("Cut invoice processing by 70%—without new software")
## CTA Best Practices
- **One primary CTA**: No competing actions; create a "one-way street" toward conversion
- **Above the fold on mobile**: Thumb-reachable; ~65%+ traffic is mobile
- **Value-focused copy**: "Start Free Trial" not "Submit"
- **Pair with trust signals**: Customer count, logos, or stats next to the button
- **Remove or minimize navigation**: Can increase conversion 2–28%
## Programmatic Landing Pages (Scale)
When you need **many landing pages** (e.g., city-specific, product-specific, integration-specific), use **programmatic-seo**: one template + data = hundreds or thousands of LPs. Apply landing page structure (5-step flow, CTA, trust) to the template; see **template-page-generator** for template design. Example: "[Product] for [City]" LPs with local data; "[App A] + [App B]" integration signup pages.
## Page Types
| Type | Use | CTA Destination |
|------|-----|-----------------|
| **Click-through** | Warm audience before sending to offer; best for SaaS, subscriptions | pricing-page, products-page, signup |
| **Lead capture** | Collect email for nurture; forms 5 fields or fewer (longer forms cause ~81% abandonment) | newsletter-signup, contact-page |
| **Product-focused** | Deep-dive features and benefits; product launch | products-page, features-page |
| **Comparison** | X vs Y; competitor brand keyword ads; commercial intent | alternatives-page, features-page, pricing-page |
| **Use cases / Solutions** | For integrated products hard to split into tools | features-page, services-page |
| **Free tools** | Standalone utilities; lead gen; same ICP; excerpt from product | tools-page-generator; tool page as LP when gated |
| **Bridge/bonus** | Extra incentive to purchase through your link | pricing-page, products-page |
| **Webinar/event** | Event registration; collect signups before live | resources-page (webinar as resource) |
## Landing Page ↔ Page Types (Content & Flow)
**Pull content from** (step 2–4):
- **customer-stories-page-generator**: Testimonials, case studies for social proof; Challenge→Solution→Results snippets
- **faq-page-generator**: Objection-handling FAQ section; reuse conversion-related Q&A
- **features-page-generator**: Benefit-first feature copy for "Explain value" step
- **resources-page-generator**: Lead magnet (ebook, template) as exchange for email; webinar as resource
**CTA sends to**:
- **pricing-page-generator**: Click-through LP → pricing; signup, trial
- **products-page-generator**: Product LP → product detail or catalog
- **services-page-generator**: Service LP → contact, quote, booking
- **contact-page-generator**: Lead capture LP → contact form; B2B demo request
- **affiliate-page-generator, creator-program**: Partner signup = landing page type
**Internal linking**:
- Link LP to **homepage** (brand anchor); **about-page** (trust); **privacy-page** (form compliance)
- Avoid orphan LPs: ensure at least one internal link from sitemap, nav, or campaign hub
## Performance and Design
- **Load time**: Under 2.5 seconds; each extra second can cost ~7% conversion
- **Mobile-first**: Responsive; CTA visible without scrolling
- **Visuals**: Hero image or video can improve conversion up to 80%
- **Frontend aesthetics**: For distinctive typography, motion, spatial composition, backgrounds—see **brand-visual-generator** Frontend Aesthetics
- **Disclosure**: FTC-compliant affiliate/paid disclosure when applicable
## Pre-Delivery Checklist
Before shipping a landing page, verify:
| Category | Check |
|----------|-------|
| **Visual** | No emojis as icons (use SVG); icons from consistent set (Heroicons/Lucide); hover states don't cause layout shift |
| **Interaction** | All clickable elements have `cursor-pointer`; hover provides clear feedback; transitions 150–300ms |
| **Accessibility** | Images have alt text; form inputs have labels; color not sole indicator; `prefers-reduced-motion` respected |
| **Layout** | No horizontal scroll on mobile; content not hidden behind fixed nav; responsive at 375px, 768px, 1024px |
| **Performance** | Load time under 2.5s; LCP optimized; images use WebP/lazy loading where appropriate |
| **Images** | See **image-optimization** for alt, format, responsive, lazy loading |
## Output Format
- **Headline** and subheadline
- **Structure** (5-step flow sections)
- **Trust signals** placement
- **CTA** copy and placement
- **Objection handling** (FAQ, guarantees)
- **Internal links** (destination pages)
- **SEO** metadata (if page is indexed)
## Related Skills
- **hero-generator**: Hero section (step 1)
- **grid, list**: Content layout below hero; sections, features, testimonials
- **cta-generator**: CTA button design and placement
- **image-optimization**: Alt, WebP, LCP, responsive, lazy loading
- **pricing-page-generator**: Click-through LP destination; signup CTA
- **faq-page-generator**: Objection-handling FAQ section
- **howto-section-generator**: How-to step section (e.g. setup flow) before FAQ/CTA
- **comparison-table-generator**: Competitor / traditional-vs-modern comparison **table section**; message match with ads
- **homepage-generator**: Multi-purpose home vs single-goal landing; similar structure
- **paid-ads-strategy**: Ad-to-page alignment; when to use paid ads
- **alternatives-page-generator**: Competitor brand keyword ads → comparison LP (not blog)
- **programmatic-seo**: Scale landing pages via template + data
- **template-page-generator**: Template structure for prograRelated 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".