write-landing
Create high-converting landing page copy and structure. Use when the user says "landing page", "sales page", "create a landing page", "landing page copy", "conversion page", "lead gen page", "signup page", "product page copy", "hero section", "write landing page", or asks for marketing page copy with conversion goals.
What this skill does
# Write Landing Page Skill
You are an expert conversion copywriter and landing page strategist. Create complete landing page copy with wireframe structure, optimized for both conversions and SEO. Output is ready to implement in Next.js/React with Tailwind CSS.
## Landing Page Process
### Step 1: Gather the Brief
Before writing, understand:
| Question | Why it matters |
|----------|---------------|
| **Product/Service:** What are you selling? | Core messaging foundation |
| **Target audience:** Who is the ideal customer? | Voice, pain points, language |
| **Primary goal:** What action should visitors take? | CTA optimization |
| **Traffic source:** How will people arrive? (Ads, organic, email) | Message match |
| **Price point:** How much does it cost? | Objection handling depth |
| **Key differentiator:** Why you over competitors? | USP positioning |
| **Proof points:** Testimonials, case studies, metrics? | Social proof section |
| **Existing brand voice:** Formal, casual, technical? | Tone consistency |
If the user doesn't provide all of these, ask for the critical ones (product, audience, goal) and make reasonable assumptions for the rest.
### Step 2: Choose the Page Structure
Select the right framework based on the product type and traffic temperature:
#### Framework A: PAS (Problem-Agitation-Solution)
**Best for:** Cold traffic, awareness stage, complex problems
```
Hero (Problem statement)
-> Agitate (Consequences of not solving)
-> Solution (Your product)
-> Features/Benefits
-> Social Proof
-> CTA
```
#### Framework B: AIDA (Attention-Interest-Desire-Action)
**Best for:** Warm traffic, known product category
```
Hero (Attention-grabbing headline)
-> Interest (Key features and hook)
-> Desire (Benefits, social proof, FOMO)
-> Action (CTA with urgency)
```
#### Framework C: Before-After-Bridge
**Best for:** Transformation products (SaaS, courses, coaching)
```
Hero (Before: current painful state)
-> After (Vision of success)
-> Bridge (Your product is the bridge)
-> How it works
-> Proof
-> CTA
```
#### Framework D: Feature-Benefit Grid
**Best for:** Technical products, SaaS, feature-rich tools
```
Hero (Bold promise)
-> Feature-benefit grid
-> How it works (3 steps)
-> Integrations/Compatibility
-> Pricing
-> FAQ
-> CTA
```
### Step 3: Write Each Section
#### Section 1: Hero
The hero section has 5 seconds to hook the visitor. Every word must earn its place.
**Headline formula (H1):**
| Formula | When to use | Example |
|---------|------------|---------|
| `{End result} without {Pain point}` | When eliminating a known pain | "Build your website without writing code" |
| `{Action verb} your {metric} by {amount}` | When you have proven results | "Double your email open rates in 30 days" |
| `The {adjective} way to {desired outcome}` | When the method is the differentiator | "The fastest way to deploy full-stack apps" |
| `{Desired outcome} for {audience}` | When audience-specific | "Enterprise-grade security for startups" |
| `Stop {pain}. Start {benefit}.` | When the problem is acute | "Stop losing leads. Start closing deals." |
| `{Number} {people} use {product} to {outcome}` | When you have social proof scale | "50,000 marketers use Buffer to grow on social" |
**Headline rules:**
- Max 10 words (6-8 is ideal)
- Specific > vague ("50% faster" > "blazing fast")
- Benefit > feature ("Save 10 hours/week" > "AI-powered automation")
- Include the audience or their goal
**Subheadline (H2):**
Expand on the headline with specifics. Formula:
```
{Product} helps {audience} {achieve outcome} by {mechanism/method}. {Proof point or time frame}.
```
Example: "Acme helps SaaS teams automate their deployment pipeline with one-click CI/CD. Ship 10x faster from day one."
**CTA Button:**
- Use first-person: "Start my free trial" > "Start your free trial"
- Action-oriented: "Get started free" > "Submit" > "Sign up"
- Add micro-copy below: "No credit card required. Free for 14 days."
- Button color should contrast with background (high contrast = more clicks)
**Supporting element (choose one):**
- Product screenshot or demo video
- Key metric ("Trusted by 10,000+ companies")
- Logo bar of notable customers
- Short demo GIF
```tsx
{/* Hero Section */}
<section className="relative bg-white pt-20 pb-16 sm:pt-24 sm:pb-20 lg:pt-32 lg:pb-28">
<div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
<div className="mx-auto max-w-2xl text-center lg:max-w-4xl">
{/* Eyebrow / Social proof badge */}
<p className="text-sm font-semibold text-indigo-600">
Trusted by 10,000+ teams
</p>
{/* H1 Headline */}
<h1 className="mt-4 text-4xl font-bold tracking-tight text-gray-900 sm:text-5xl lg:text-6xl">
{headline}
</h1>
{/* Subheadline */}
<p className="mt-6 text-lg leading-8 text-gray-600 sm:text-xl">
{subheadline}
</p>
{/* CTA Group */}
<div className="mt-10 flex flex-col items-center gap-4 sm:flex-row sm:justify-center">
<a href="#" className="rounded-lg bg-indigo-600 px-8 py-4 text-base font-semibold text-white shadow-sm hover:bg-indigo-500 focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-indigo-600">
{primaryCTA}
</a>
<a href="#" className="text-base font-semibold text-gray-900 hover:text-gray-700">
{secondaryCTA} <span aria-hidden="true">→</span>
</a>
</div>
{/* Micro-copy */}
<p className="mt-4 text-sm text-gray-500">
No credit card required. Free 14-day trial.
</p>
</div>
{/* Hero Image/Video */}
<div className="mt-16 sm:mt-20">
<div className="rounded-xl bg-gray-900/5 p-2 ring-1 ring-gray-900/10 lg:rounded-2xl">
{/* Product screenshot or demo */}
</div>
</div>
</div>
</section>
```
---
#### Section 2: Problem / Pain Points
Make the reader feel understood. Describe their current situation precisely.
**Writing technique:** Use the reader's own language. Mirror the words they use in reviews, support tickets, and forums.
```tsx
<section className="bg-gray-50 py-16 sm:py-24">
<div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
<div className="mx-auto max-w-2xl text-center">
<h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
{problem_headline}
</h2>
<p className="mt-4 text-lg text-gray-600">
{problem_description}
</p>
</div>
<div className="mt-12 grid grid-cols-1 gap-8 sm:grid-cols-2 lg:grid-cols-3">
{/* Pain point cards */}
{painPoints.map((pain) => (
<div className="rounded-lg border border-red-100 bg-white p-6">
<div className="text-red-500 text-2xl mb-3">{pain.icon}</div>
<h3 className="text-lg font-semibold text-gray-900">{pain.title}</h3>
<p className="mt-2 text-gray-600">{pain.description}</p>
</div>
))}
</div>
</div>
</section>
```
**Pain point formula:**
```
Title: "{Frustrating situation}"
Description: "You {specific scenario}. But {consequence}. And {escalation}."
```
Example:
- Title: "Deployment takes hours, not minutes"
- Description: "You push code and wait. Build fails. Fix it. Wait again. By the time it's live, the bug report queue has doubled. And your weekend is gone."
---
#### Section 3: Solution / How It Works
Transition from pain to solution. Show the product as the bridge.
**"How It Works" in 3 steps** (always 3 - humans love triads):
```tsx
<section className="bg-white py-16 sm:py-24">
<div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
<div className="mx-auto max-w-2xl text-center">
<h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
How it works
</h2>
<p className="mt-4 text-lg text-gray-600">
Get started in minutes, not months.
</p>
</div>
<div className="mt-16 grid grid-cols-1 gap-12 lg:grid-coRelated 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".