diff --git a/skills/landing-page-generator/SKILL.md b/skills/landing-page-generator/SKILL.md
new file mode 100644
index 00000000..ab6237d7
--- /dev/null
+++ b/skills/landing-page-generator/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: "landing-page-generator"
+description: "Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO."
+category: "front-end"
+risk: "safe"
+source: "community"
+date_added: "2026-03-18"
+author: "alirezarezvani"
+tags: ["nextjs", "react", "tailwind", "landing-page", "marketing", "seo", "cro"]
+tools: ["claude", "cursor", "gemini"]
+---
+
+# Landing Page Generator
+
+Generate high-converting landing pages from a product description. Output complete Next.js/React components with multiple section variants, proven copy frameworks, SEO optimization, and performance-first patterns. Not lorem ipsum — actual copy that converts.
+
+**Target:** LCP < 1s · CLS < 0.1 · FID < 100ms
+**Output:** TSX components + Tailwind styles + SEO meta + copy variants
+
+## Core Capabilities
+
+- 5 hero section variants (centered, split, gradient, video-bg, minimal)
+- Feature sections (grid, alternating, cards with icons)
+- Pricing tables (2–4 tiers with feature lists and toggle)
+- FAQ accordion with schema markup
+- Testimonials (grid, carousel, single-quote)
+- CTA sections (banner, full-page, inline)
+- Footer (simple, mega, minimal)
+- 4 design styles with Tailwind class sets
+
+---
+
+## Generation Workflow
+
+Follow these steps in order for every landing page request:
+
+1. **Gather inputs** — collect product name, tagline, audience, pain point, key benefit, pricing tiers, design style, and copy framework using the trigger format below. Ask only for missing fields.
+2. **Analyze brand voice** (recommended) — if the user has existing brand content (website copy, blog posts, marketing materials), run it through `marketing-skill/content-production/scripts/brand_voice_analyzer.py` to get a voice profile (formality, tone, perspective). Use the profile to inform design style and copy framework selection:
+ - formal + professional → **enterprise** style, **AIDA** framework
+ - casual + friendly → **bold-startup** style, **BAB** framework
+ - professional + authoritative → **dark-saas** style, **PAS** framework
+ - casual + conversational → **clean-minimal** style, **BAB** framework
+3. **Select design style** — map the user's choice (or infer from brand voice analysis) to one of the four Tailwind class sets in the Design Style Reference.
+4. **Apply copy framework** — write all headline and body copy using the chosen framework (PAS / AIDA / BAB) before generating components. Match the voice profile's formality and tone throughout.
+5. **Generate sections in order** — Hero → Features → Pricing → FAQ → Testimonials → CTA → Footer. Skip sections not relevant to the product.
+6. **Validate against SEO checklist** — run through every item in the SEO Checklist before outputting final code. Fix any gaps inline.
+7. **Output final components** — deliver complete, copy-paste-ready TSX files with all Tailwind classes, SEO meta, and structured data included.
+
+---
+
+## Triggering This Skill
+
+```
+Product: [name]
+Tagline: [one sentence value prop]
+Target audience: [who they are]
+Key pain point: [what problem you solve]
+Key benefit: [primary outcome]
+Pricing tiers: [free/pro/enterprise or describe]
+Design style: dark-saas | clean-minimal | bold-startup | enterprise
+Copy framework: PAS | AIDA | BAB
+```
+
+---
+
+## Design Style Reference
+
+| Style | Background | Accent | Cards | CTA Button |
+|---|---|---|---|---|
+| **Dark SaaS** | `bg-gray-950 text-white` | `violet-500/400` | `bg-gray-900 border border-gray-800` | `bg-violet-600 hover:bg-violet-500` |
+| **Clean Minimal** | `bg-white text-gray-900` | `blue-600` | `bg-gray-50 border border-gray-200 rounded-2xl` | `bg-blue-600 hover:bg-blue-700` |
+| **Bold Startup** | `bg-white text-gray-900` | `orange-500` | `shadow-xl rounded-3xl` | `bg-orange-500 hover:bg-orange-600 text-white` |
+| **Enterprise** | `bg-slate-50 text-slate-900` | `slate-700` | `bg-white border border-slate-200 shadow-sm` | `bg-slate-900 hover:bg-slate-800 text-white` |
+
+> **Bold Startup** headings: add `font-black tracking-tight` to all `
`/`
` elements.
+
+---
+
+## Copy Frameworks
+
+**PAS (Problem → Agitate → Solution)**
+- H1: Painful state they're in
+- Sub: What happens if they don't fix it
+- CTA: What you offer
+- *Example — H1:* "Your team wastes 3 hours a day on manual reporting" / *Sub:* "Every hour spent on spreadsheets is an hour not closing deals. Your competitors are already automated." / *CTA:* "Automate your reports in 10 minutes →"
+
+**AIDA (Attention → Interest → Desire → Action)**
+- H1: Bold attention-grabbing statement → Sub: Interesting fact or benefit → Features: Desire-building proof points → CTA: Clear action
+
+**BAB (Before → After → Bridge)**
+- H1: "[Before state] → [After state]" → Sub: "Here's how [product] bridges the gap" → Features: How it works (the bridge)
+
+---
+
+## Representative Component: Hero (Centered Gradient — Dark SaaS)
+
+Use this as the structural template for all hero variants. Swap layout classes, gradient direction, and image placement for split, video-bg, and minimal variants.
+
+```tsx
+export function HeroCentered() {
+ return (
+
+
+
+
+
+
+ Now in public beta
+
+
+ Ship faster.
+
+ Break less.
+
+
+
+ The deployment platform that catches errors before your users do.
+ Zero config. Instant rollbacks. Real-time monitoring.
+
+
+
+
+
+
No credit card required · 14-day free trial
+
+
+ )
+}
+```
+
+---
+
+## Other Section Patterns
+
+### Feature Section (Alternating)
+
+Map over a `features` array with `{ title, description, image, badge }`. Toggle layout direction with `i % 2 === 1 ? "lg:flex-row-reverse" : ""`. Use `` with explicit `width`/`height` and `rounded-2xl shadow-xl`. Wrap in `` with `max-w-6xl` container.
+
+### Pricing Table
+
+Map over a `plans` array with `{ name, price, description, features[], cta, highlighted }`. Highlighted plan gets `border-2 border-violet-500 bg-violet-950/50 ring-4 ring-violet-500/20`; others get `border border-gray-800 bg-gray-900`. Render `null` price as "Custom". Use `` icon per feature row. Layout: `grid gap-8 lg:grid-cols-3`.
+
+### FAQ with Schema Markup
+
+Inject `FAQPage` JSON-LD via `` inside the section. Map FAQs with `{ q, a }` into shadcn `` with `type="single" collapsible`. Container: `max-w-3xl`.
+
+### Testimonials, CTA, Footer
+
+- **Testimonials:** Grid (`grid-cols-1 md:grid-cols-3`) or single-quote hero block with avatar, name, role, and quote text.
+- **CTA Banner:** Full-width section with headline, subhead, and two buttons (primary + ghost). Add trust signals (money-back guarantee, logo strip) immediately below.
+- **Footer:** Logo + nav columns + social links + legal. Use `border-t border-gray-800` separator.
+
+---
+
+## SEO Checklist
+
+- [ ] `` tag: primary keyword + brand (50–60 chars)
+- [ ] Meta description: benefit + CTA (150–160 chars)
+- [ ] OG image: 1200×630px with product name and tagline
+- [ ] H1: one per page, includes primary keyword
+- [ ] Structured data: FAQPage, Product, or Organization schema
+- [ ] Canonical URL set
+- [ ] Image alt text on all `` components
+- [ ] robots.txt and sitemap.xml configured
+- [ ] Core Web Vitals: LCP < 1s, CLS < 0.1
+- [ ] Mobile viewport meta tag present
+- [ ] Internal linking to pricing and docs
+
+> **Validation step:** Before outputting final code, verify every checklist item above is satisfied. Fix any gaps inline — do not skip items.
+
+---
+
+## Performance Targets
+
+| Metric | Target | Technique |
+|---|---|---|
+| LCP | < 1s | Preload hero image, use `priority` on Next/Image |
+| CLS | < 0.1 | Set explicit width/height on all images |
+| FID/INP | < 100ms | Defer non-critical JS, use `loading="lazy"` |
+| TTFB | < 200ms | Use ISR or static generation for landing pages |
+| Bundle | < 100KB JS | Audit with `@next/bundle-analyzer` |
+
+---
+
+## Common Pitfalls
+
+- Hero image not preloaded — add `priority` prop to first ``
+- Missing mobile breakpoints — always design mobile-first with `sm:` prefixes
+- CTA copy too vague — "Get started" beats "Learn more"; "Start free trial" beats "Sign up"
+- Pricing page missing trust signals — add money-back guarantee and testimonials near CTA
+- No above-the-fold CTA on mobile — ensure button is visible without scrolling on 375px viewport
+
+---
+
+## Related Skills
+
+- **Brand Voice Analyzer** (`marketing-skill/content-production/scripts/brand_voice_analyzer.py`) — Run before generation to establish voice profile and ensure copy consistency
+- **UI Design System** (`product-team/ui-design-system/`) — Generate design tokens from brand color before building the page
+- **Competitive Teardown** (`product-team/competitive-teardown/`) — Competitive positioning informs landing page messaging and differentiation
diff --git a/skills/landing-page-generator/references/conversion-patterns.md b/skills/landing-page-generator/references/conversion-patterns.md
new file mode 100644
index 00000000..74c9b70d
--- /dev/null
+++ b/skills/landing-page-generator/references/conversion-patterns.md
@@ -0,0 +1,176 @@
+# High-Converting Landing Page Patterns
+
+## Overview
+
+This reference catalogs proven landing page design patterns that drive higher conversion rates. Each pattern includes placement guidance, implementation notes, and A/B testing priorities.
+
+## Hero Section Layouts
+
+### Pattern 1: Left Copy + Right Product Screenshot
+- **Best for:** SaaS products with a strong visual UI
+- **Structure:** Headline, subheadline, CTA on left (60%); product screenshot on right (40%)
+- **Why it works:** F-pattern reading leads with copy, product image provides proof
+- **Conversion lift:** Baseline pattern, strong performer across industries
+
+### Pattern 2: Centered Copy + Full-Width Background
+- **Best for:** Brand-driven products, consumer apps
+- **Structure:** Centered headline, subheadline, CTA over background image/gradient
+- **Why it works:** Focuses attention on single message, high visual impact
+- **Note:** Ensure text contrast against background for readability
+
+### Pattern 3: Video Hero
+- **Best for:** Complex products requiring demonstration
+- **Structure:** Short headline + embedded video (60-90 seconds) + CTA below
+- **Why it works:** Video explains what text cannot, increases time on page
+- **Note:** Always include thumbnail; autoplay is often counterproductive
+
+### Pattern 4: Interactive Demo
+- **Best for:** Developer tools, data products, design tools
+- **Structure:** Minimal copy + embedded interactive product experience
+- **Why it works:** Hands-on experience converts better than description
+- **Note:** Keep demo focused on one "aha moment" workflow
+
+## Social Proof Placement
+
+### Logo Bar
+- **Position:** Immediately below hero section
+- **Count:** 5-7 logos for credibility without clutter
+- **Label:** "Trusted by" or "Used by teams at"
+- **Selection:** Mix recognizable brands with relevant industry logos
+
+### Testimonial Cards
+- **Position:** After feature explanation sections
+- **Format:** Photo + name + title + company + specific quote
+- **Best quotes:** Include measurable outcomes ("Saved 10 hours/week")
+- **Layout:** 2-3 testimonials in a row, carousel for more
+
+### Case Study Callouts
+- **Position:** Mid-page, before pricing
+- **Format:** Company logo + headline metric + "Read the story" link
+- **Example:** "Acme Corp reduced onboarding time by 60%"
+
+### Social Proof Numbers
+- **Position:** Near CTA or in dedicated trust section
+- **Format:** Large number + descriptor (e.g., "50,000+ teams", "4.8/5 rating")
+- **Selection:** Choose 3-4 most impressive metrics
+
+## Pricing Table Designs
+
+### Good/Better/Best (3-Tier)
+- Most effective for SaaS with clear feature tiers
+- Highlight recommended plan with visual emphasis
+- Show annual discount prominently
+- Include feature comparison matrix below
+
+### Simple Two-Tier
+- Free/Pro or Starter/Professional
+- Best for PLG products with clear upgrade trigger
+- Minimize decision fatigue
+
+### Enterprise Custom
+- Replace price with "Contact Sales" for high-ACV products
+- List enterprise-specific features (SSO, SLA, dedicated support)
+- Include a "Talk to Sales" CTA, not just a form
+
+### Pricing Psychology
+- Anchor with highest-priced plan first (or in the middle with visual highlight)
+- Use monthly price with annual billing toggle
+- Show savings percentage for annual plans
+- Round prices ending in 9 (e.g., $49/mo, $99/mo)
+
+## Trust Signals
+
+### Security Badges
+- SOC 2, ISO 27001, GDPR compliance badges
+- SSL certificate indicator
+- Place near forms and payment sections
+
+### Guarantees
+- Money-back guarantee with specific timeframe
+- Free trial with no credit card requirement
+- SLA uptime commitments
+
+### Awards & Recognition
+- Industry awards (best of, top rated)
+- Analyst recognition (Gartner, Forrester, G2 Leader)
+- Media mentions (as seen in logos)
+
+### Real-Time Activity
+- "X people signed up today" (use real data only)
+- Recent activity feed
+- Live user count
+
+## Urgency Elements
+
+### Ethical Urgency
+- Limited-time pricing (with real deadline)
+- Early adopter benefits (extra features, lower price)
+- Cohort-based enrollment (actual capacity limits)
+
+### Avoid
+- Fake countdown timers that reset
+- False scarcity ("only 3 left" when unlimited)
+- Pressure tactics that erode trust
+
+## Form Optimization
+
+### Field Reduction
+- Every additional field reduces conversion ~10%
+- Start with email only, progressive profiling later
+- Use single-column layouts for forms
+
+### Smart Defaults
+- Pre-fill country based on IP
+- Auto-detect company from email domain
+- Default to most popular plan
+
+### Inline Validation
+- Validate fields on blur, not on submit
+- Show success states (green checkmark)
+- Provide helpful error messages
+
+### Multi-Step Forms
+- Break long forms into 2-3 steps with progress indicator
+- Put easiest questions first to build commitment
+- Allow saving progress for complex forms
+
+## Mobile-First Patterns
+
+### Thumb-Friendly Design
+- CTAs in thumb zone (bottom 40% of screen)
+- Minimum tap target: 44x44px
+- Adequate spacing between interactive elements
+
+### Content Priority
+- Lead with most compelling content (no scrolling to find CTA)
+- Collapse secondary information into accordions
+- Use sticky CTA bar on scroll
+
+### Performance
+- Target <3s load time on 3G
+- Lazy-load images below fold
+- Minimize JavaScript execution
+
+## A/B Testing Priority Matrix
+
+Test these elements in order of expected impact:
+
+| Priority | Element | Expected Impact | Effort |
+|----------|---------|----------------|--------|
+| 1 | Headline | High | Low |
+| 2 | CTA text and color | High | Low |
+| 3 | Hero image/video | High | Medium |
+| 4 | Social proof placement | Medium | Low |
+| 5 | Form fields (fewer) | Medium | Low |
+| 6 | Pricing presentation | Medium | Medium |
+| 7 | Page length | Medium | High |
+| 8 | Testimonial selection | Low | Low |
+| 9 | Color scheme | Low | Medium |
+| 10 | Font choices | Low | Low |
+
+### Testing Best Practices
+- Test one variable at a time for clear attribution
+- Run tests for minimum 2 weeks or 1,000 visitors per variant
+- Use 95% statistical significance threshold
+- Document all test results for institutional knowledge
+- Winner becomes new control for next test iteration
diff --git a/skills/landing-page-generator/references/frameworks.md b/skills/landing-page-generator/references/frameworks.md
new file mode 100644
index 00000000..61883bf8
--- /dev/null
+++ b/skills/landing-page-generator/references/frameworks.md
@@ -0,0 +1,177 @@
+# Landing Page Copywriting Frameworks
+
+## Overview
+
+Four copy frameworks with worked SaaS examples you can adapt. Each framework includes a complete before/after example plus specific guidelines for each section.
+
+## 1. AIDA Framework (Attention - Interest - Desire - Action)
+
+The classic direct response formula, ideal for product landing pages.
+
+**Example — Project management SaaS:**
+
+> **Attention:** "Your Team Loses 12 Hours Every Sprint to Status Meetings"
+>
+> **Interest:** "Engineering teams at Series A-C startups spend 23% of their week in sync meetings — not writing code. We tracked 847 teams over 6 months. The pattern was clear: the more people in a standup, the less code shipped that day."
+>
+> **Desire:** "Teams using AsyncStand ship 31% more story points per sprint. No more 15-person standups where 13 people zone out. Replace your daily sync with a 2-minute async check-in that your engineers actually complete (94% response rate vs 67% attendance for live standups)."
+>
+> **Action:** "Start Your Free 14-Day Trial — No Credit Card Required"
+
+### Attention
+- Lead with a specific, quantified pain point (not vague claims)
+- Weak: "Save time on meetings" → Strong: "Your Team Loses 12 Hours Every Sprint to Status Meetings"
+- Keep headlines under 10 words for maximum impact
+
+### Interest
+- Back up the headline with specific data or a relatable scenario
+- Weak: "Meetings waste time" → Strong: "We tracked 847 teams — the more people in standup, the less code shipped that day"
+- Use their language: mirror words from customer reviews, support tickets, and G2 feedback
+
+### Desire
+- Stack measurable outcomes, not features
+- Weak: "AI-powered async updates" → Strong: "31% more story points per sprint, 94% response rate"
+- Compare directly to the status quo they already endure
+
+### Action
+- Single, clear CTA with action-oriented verb
+- Reduce friction: "No credit card required," "Set up in 2 minutes"
+- Repeat CTA after each major content block
+
+## 2. PAS Framework (Problem - Agitate - Solution)
+
+Best for pain-point-driven products where the problem is well understood.
+
+**Example — Expense management tool:**
+
+> **Problem:** "Your finance team is still chasing receipts in Slack DMs."
+>
+> **Agitate:** "Last quarter, your team spent 46 hours manually reconciling expenses across email threads, shared drives, and 'I'll submit it later' promises. That's $4,200 in payroll — spent on data entry. And when audit season hits? Good luck finding that client dinner receipt from February."
+>
+> **Solution:** "Snap a photo of the receipt. ExpenseFlow auto-extracts vendor, amount, and category in 3 seconds. Your monthly close drops from 5 days to 1. 2,400 finance teams already made the switch."
+
+### Problem
+- Name the exact scenario (not the abstract category)
+- Weak: "Expense tracking is hard" → Strong: "Your finance team is still chasing receipts in Slack DMs"
+- Mirror language from reviews and support tickets
+
+### Agitate
+- Quantify the cost in dollars, hours, or missed opportunities
+- Weak: "This costs you money" → Strong: "46 hours last quarter, $4,200 in payroll — on data entry"
+- Acknowledge the workarounds they've tried and why those fail too
+
+### Solution
+- Lead with the user action, not the technology: "Snap a photo" not "AI-powered OCR"
+- Include one proof point: number of customers, time saved, or before/after metric
+- Make the mechanism clear in one sentence: what happens when they use it
+
+## 3. BAB Framework (Before - After - Bridge)
+
+Ideal for aspirational products and lifestyle-oriented landing pages.
+
+**Example — Sales enablement platform:**
+
+> **Before:** "It's 9 PM. You're rebuilding a deck for tomorrow's demo because the prospect is in healthcare, not fintech. You copy-paste from three old decks, pray the logos are right, and rehearse the new talk track in the shower."
+>
+> **After:** "It's 9 AM. You type 'healthcare, 200-bed hospital, HIPAA-concerned CTO.' DeckGen builds your slides in 40 seconds — case studies, compliance badges, ROI calculator pre-loaded. You walk into the call with the best deck your prospect has ever seen."
+>
+> **Bridge:** "DeckGen connects to your CRM, learns your win patterns, and generates prospect-specific decks in under a minute. 340 AEs at companies like Stripe and Notion already use it. Start free — your first 5 decks are on us."
+
+### Before
+- Describe a specific, lived moment — not an abstract pain category
+- Weak: "Sales decks take too long" → Strong: "It's 9 PM. You're rebuilding a deck for tomorrow's demo..."
+- Use second person and present tense to make it feel immediate
+
+### After
+- Same level of specificity — show the transformed version of that exact moment
+- Include a measurable outcome: "40 seconds," "best deck your prospect has ever seen"
+- The after state should feel effortless compared to the before
+
+### Bridge
+- Name the product explicitly and explain the mechanism in one sentence
+- Include one social proof data point
+- End with a low-friction CTA that connects to the after state
+
+## 4. 4Ps Framework (Promise - Picture - Proof - Push)
+
+Strong for SaaS and B2B landing pages with measurable outcomes.
+
+### Promise
+- Make a clear, specific, believable promise
+- Tie it to a measurable outcome
+- Example: "Reduce customer churn by 25% in 90 days"
+
+### Picture
+- Help the reader visualize success
+- Use scenarios they can relate to
+- Show the product in context (screenshots, demos)
+
+### Proof
+- Back the promise with evidence
+- Customer testimonials with specific results
+- Case studies with before/after metrics
+- Third-party validation (awards, analyst reports)
+
+### Push
+- Give a compelling reason to act now
+- Limited-time offer, bonus, or guarantee
+- Risk reversal (money-back guarantee, free trial)
+
+## Headline Formulas
+
+### Benefit-Driven
+- "Get [Desired Outcome] Without [Common Objection]"
+- "[Specific Result] in [Timeframe]"
+- "The [Adjective] Way to [Achieve Goal]"
+
+### Problem-Driven
+- "Stop [Painful Activity]. Start [Better Alternative]."
+- "Tired of [Problem]? There's a Better Way."
+- "[Problem]? Not Anymore."
+
+### Social Proof-Driven
+- "[Number] Teams Trust [Product] to [Outcome]"
+- "Why [Notable Company] Switched to [Product]"
+- "Rated #1 for [Category] by [Authority]"
+
+### Question-Driven
+- "What If You Could [Desirable Outcome]?"
+- "Ready to [Transformation]?"
+- "Still [Painful Status Quo]?"
+
+## CTA Best Practices
+
+### Language
+- Use first-person: "Start My Free Trial" > "Start Your Free Trial"
+- Be specific: "Get My Report" > "Submit"
+- Include benefit: "Start Saving Time" > "Sign Up"
+- Add urgency naturally: "Start Free Today" > "Sign Up Now!!!"
+
+### Placement
+- Primary CTA above the fold
+- Repeat after each major content section
+- Sticky CTA on scroll (mobile especially)
+- Exit-intent as last chance
+
+### Design
+- High contrast color (stands out from page palette)
+- Sufficient whitespace around the button
+- Large enough to tap on mobile (min 44x44px)
+- Micro-copy below button to reduce anxiety ("No credit card required")
+
+## Above-the-Fold Principles
+
+The first viewport must accomplish these goals within 5 seconds:
+1. **Communicate what you do** - Clear, jargon-free headline
+2. **Show who it's for** - Audience identification
+3. **Demonstrate value** - Primary benefit or outcome
+4. **Provide next step** - Visible CTA button
+5. **Build credibility** - One trust signal (logo bar, metric, badge)
+
+### Above-the-Fold Checklist
+- [ ] Headline states primary benefit (under 10 words)
+- [ ] Subheadline adds specificity or addresses objection
+- [ ] Hero image/video shows product in use
+- [ ] CTA button is visible without scrolling
+- [ ] At least one trust signal present
+- [ ] No jargon or ambiguity in messaging
diff --git a/skills/landing-page-generator/references/landing-page-patterns.md b/skills/landing-page-generator/references/landing-page-patterns.md
new file mode 100644
index 00000000..e419448a
--- /dev/null
+++ b/skills/landing-page-generator/references/landing-page-patterns.md
@@ -0,0 +1,98 @@
+# Landing Page Patterns
+
+This reference captures high-converting page patterns and copy structures.
+
+## Hero Section Patterns
+
+### Pattern 1: Problem-Solution Hero
+- Headline names the painful problem.
+- Subheadline states the clear outcome.
+- Primary CTA starts immediately.
+- Optional supporting visual demonstrates product in context.
+
+### Pattern 2: Outcome-First Hero
+- Headline leads with measurable value.
+- Subheadline clarifies who the page is for.
+- CTA is action-oriented and specific.
+
+### Pattern 3: Authority Hero
+- Headline + trust indicator (logos, testimonial snippet, proof metric).
+- Useful when category skepticism is high.
+
+## Social Proof Layouts
+
+### Logo Strip + Proof Metric
+- Keep to recognizable logos.
+- Add one proof metric (e.g., active users, revenue saved, hours reduced).
+
+### Testimonial Grid
+- 3-6 testimonials across segments.
+- Include role/company where possible.
+- Prefer concrete outcomes over generic praise.
+
+### Case Study Snapshot
+- Mini blocks: challenge -> approach -> measurable result.
+
+## CTA Best Practices
+
+- Use one dominant CTA per section.
+- Match CTA verb to user intent ("Start trial", "Get demo", "Run audit").
+- Keep CTA copy specific; avoid vague labels like "Submit".
+- Reduce friction near CTA (short form, trust indicators, no surprise commitments).
+
+## Above-the-Fold Checklist
+
+- [ ] Clear value proposition in first viewport
+- [ ] Audience clarity (who this is for)
+- [ ] One primary CTA visible without scrolling
+- [ ] Proof element (logos, stat, quote)
+- [ ] Visual hierarchy emphasizes headline + CTA
+- [ ] Mobile layout keeps CTA accessible
+
+## Conversion-Optimized Templates
+
+### SaaS Demo Page
+1. Hero with problem-solution framing
+2. Product walkthrough section
+3. Social proof strip
+4. Benefits by persona
+5. Objection handling FAQ
+6. Final CTA
+
+### Lead Magnet Page
+1. Promise + asset preview
+2. Bullet outcomes
+3. Short form
+4. Trust/privacy note
+
+### Product Launch Page
+1. Outcome-first hero
+2. Why now / differentiation
+3. Feature blocks
+4. Testimonials / beta feedback
+5. Pricing or waitlist CTA
+
+## Headline Formulas
+
+### PAS (Problem-Agitate-Solution)
+- Problem: identify the pain
+- Agitate: show consequences of inaction
+- Solution: position the offer as relief
+
+Example structure:
+"Still [problem]? Stop [negative consequence] and start [desired outcome]."
+
+### AIDA (Attention-Interest-Desire-Action)
+- Attention: pattern interrupt headline
+- Interest: relevant context and stakes
+- Desire: proof and benefits
+- Action: concrete next step
+
+### 4U Formula
+- Useful: clear practical value
+- Urgent: reason to act now
+- Unique: differentiated promise
+- Ultra-specific: concrete outcome and scope
+
+Example structure:
+"Get [specific result] in [timeframe] without [common pain]."
diff --git a/skills/landing-page-generator/references/seo-checklist.md b/skills/landing-page-generator/references/seo-checklist.md
new file mode 100644
index 00000000..59a858fc
--- /dev/null
+++ b/skills/landing-page-generator/references/seo-checklist.md
@@ -0,0 +1,109 @@
+# Landing Page SEO Checklist
+
+## Overview
+
+This checklist ensures landing pages are optimized for search engine visibility while maintaining conversion focus. Apply these checks before launching any landing page.
+
+## Meta Tags
+
+- [ ] **Title tag**: Under 60 characters, includes primary keyword, ends with brand name
+- [ ] **Meta description**: 150-160 characters, includes CTA language, unique per page
+- [ ] **Canonical URL**: Set to prevent duplicate content issues
+- [ ] **Robots meta**: Ensure page is indexable (`index, follow`) unless intentionally noindex
+- [ ] **Open Graph tags**: og:title, og:description, og:image, og:url for social sharing
+- [ ] **Twitter Card tags**: twitter:card, twitter:title, twitter:description, twitter:image
+- [ ] **Viewport meta**: ``
+
+## Structured Data
+
+- [ ] **Organization schema**: Company name, logo, social profiles
+- [ ] **Product schema**: Name, description, price, availability (for product pages)
+- [ ] **FAQ schema**: For pages with FAQ sections (rich snippet opportunity)
+- [ ] **Breadcrumb schema**: Navigation path for deep pages
+- [ ] **Review schema**: Aggregate rating if testimonials present (use carefully per guidelines)
+- [ ] **Validate**: Test all structured data with Google Rich Results Test
+
+## Core Web Vitals Targets
+
+### Largest Contentful Paint (LCP) - Target: < 2.5s
+- [ ] Optimize hero image (WebP format, proper dimensions)
+- [ ] Preload critical resources (``)
+- [ ] Use CDN for static assets
+- [ ] Minimize render-blocking CSS and JavaScript
+
+### First Input Delay (FID) / Interaction to Next Paint (INP) - Target: < 200ms
+- [ ] Defer non-critical JavaScript
+- [ ] Break up long tasks (>50ms)
+- [ ] Minimize third-party script impact
+- [ ] Use `requestAnimationFrame` for visual updates
+
+### Cumulative Layout Shift (CLS) - Target: < 0.1
+- [ ] Set explicit width/height on images and videos
+- [ ] Reserve space for dynamic content (ads, embeds)
+- [ ] Use `font-display: swap` for web fonts
+- [ ] Avoid inserting content above existing content
+
+## Keyword Placement
+
+- [ ] **H1 tag**: Contains primary keyword, one per page only
+- [ ] **H2 tags**: Include secondary keywords naturally
+- [ ] **First paragraph**: Primary keyword appears in first 100 words
+- [ ] **Body copy**: Natural keyword density (1-2%), no stuffing
+- [ ] **Image alt text**: Descriptive, includes keyword where relevant
+- [ ] **URL slug**: Short, keyword-rich, hyphen-separated
+- [ ] **CTA text**: Consider keyword inclusion where natural
+
+## Internal Linking
+
+- [ ] Link to relevant product/feature pages
+- [ ] Link to blog content that supports the page topic
+- [ ] Use descriptive anchor text (not "click here")
+- [ ] Ensure landing page is linked from main navigation or sitemap
+- [ ] Link to pricing page if applicable
+- [ ] Limit links to avoid diluting page authority (15-20 max)
+
+## Image Optimization
+
+- [ ] **Format**: Use WebP with JPEG/PNG fallback
+- [ ] **Compression**: Lossy compression for photos, lossless for graphics
+- [ ] **Dimensions**: Serve at exact display size (no CSS resizing)
+- [ ] **Alt text**: Descriptive, 125 characters max, natural keyword inclusion
+- [ ] **File names**: Descriptive, hyphenated (e.g., `product-dashboard-screenshot.webp`)
+- [ ] **Lazy loading**: Apply to images below the fold (`loading="lazy"`)
+- [ ] **Responsive images**: Use `srcset` for different viewport sizes
+
+## Canonical URLs
+
+- [ ] Self-referencing canonical on every page
+- [ ] Consistent protocol (https) and trailing slash usage
+- [ ] Canonical points to preferred URL version (www vs non-www)
+- [ ] UTM parameters excluded from canonical URL
+- [ ] Pagination handled with rel="next"/"prev" or single-page canonical
+
+## Mobile Responsiveness
+
+- [ ] **Mobile-friendly test**: Pass Google Mobile-Friendly Test
+- [ ] **Touch targets**: Minimum 44x44px, 8px spacing between targets
+- [ ] **Font size**: Minimum 16px base font, no pinch-to-zoom needed
+- [ ] **Content parity**: All critical content accessible on mobile
+- [ ] **Horizontal scroll**: None present at any viewport width
+- [ ] **Form usability**: Appropriate input types (email, tel), autocomplete attributes
+- [ ] **Media queries**: Breakpoints at 480px, 768px, 1024px, 1200px minimum
+
+## Technical SEO
+
+- [ ] **HTTPS**: SSL certificate valid and active
+- [ ] **Page speed**: < 3s load time on mobile (test with PageSpeed Insights)
+- [ ] **XML sitemap**: Page included in sitemap.xml
+- [ ] **Robots.txt**: Page not blocked by robots.txt
+- [ ] **404 handling**: Custom 404 page with navigation
+- [ ] **Redirect chains**: No more than 1 redirect hop
+- [ ] **Hreflang**: Set for multi-language landing pages
+
+## Content Quality Signals
+
+- [ ] **Unique content**: No duplicate content from other pages
+- [ ] **Content depth**: Sufficient content for topic coverage (500+ words for SEO pages)
+- [ ] **Readability**: Grade level 6-8 for broad audiences
+- [ ] **Freshness**: Last modified date reflects recent updates
+- [ ] **E-E-A-T signals**: Author expertise, company authority, trust indicators
diff --git a/skills/landing-page-generator/scripts/landing_page_scaffolder.py b/skills/landing-page-generator/scripts/landing_page_scaffolder.py
new file mode 100644
index 00000000..cf071862
--- /dev/null
+++ b/skills/landing-page-generator/scripts/landing_page_scaffolder.py
@@ -0,0 +1,568 @@
+#!/usr/bin/env python3
+"""Landing Page Scaffolder — Generate landing pages as HTML or Next.js TSX from config.
+
+Creates production-ready landing pages with hero sections, features,
+testimonials, pricing, CTAs, and responsive design.
+
+Usage:
+ python landing_page_scaffolder.py config.json --format html --output page.html
+ python landing_page_scaffolder.py config.json --format tsx --output LandingPage.tsx
+ python landing_page_scaffolder.py config.json --format json
+"""
+
+import argparse
+import json
+import sys
+from typing import Dict, List, Any, Optional
+from datetime import datetime
+import html as html_module
+
+
+def escape(text: str) -> str:
+ """HTML-escape text."""
+ return html_module.escape(str(text))
+
+
+# ---------------------------------------------------------------------------
+# Tailwind style mappings for TSX output
+# ---------------------------------------------------------------------------
+
+DESIGN_STYLES = {
+ "dark-saas": {
+ "bg": "bg-gray-950", "text": "text-white",
+ "accent": "violet", "card_bg": "bg-gray-900 border border-gray-800",
+ "btn": "bg-violet-600 hover:bg-violet-500 text-white",
+ "btn_secondary": "border border-gray-700 text-gray-300 hover:bg-gray-800",
+ "section_alt": "bg-gray-900/50", "muted": "text-gray-400",
+ "border": "border-gray-800",
+ },
+ "clean-minimal": {
+ "bg": "bg-white", "text": "text-gray-900",
+ "accent": "blue", "card_bg": "bg-gray-50 border border-gray-200 rounded-2xl",
+ "btn": "bg-blue-600 hover:bg-blue-700 text-white",
+ "btn_secondary": "border border-gray-300 text-gray-700 hover:bg-gray-50",
+ "section_alt": "bg-gray-50", "muted": "text-gray-500",
+ "border": "border-gray-200",
+ },
+ "bold-startup": {
+ "bg": "bg-white", "text": "text-gray-900",
+ "accent": "orange", "card_bg": "shadow-xl rounded-3xl bg-white",
+ "btn": "bg-orange-500 hover:bg-orange-600 text-white",
+ "btn_secondary": "border-2 border-orange-500 text-orange-600 hover:bg-orange-50",
+ "section_alt": "bg-orange-50/30", "muted": "text-gray-500",
+ "border": "border-gray-200",
+ },
+ "enterprise": {
+ "bg": "bg-slate-50", "text": "text-slate-900",
+ "accent": "slate", "card_bg": "bg-white border border-slate-200 shadow-sm",
+ "btn": "bg-slate-900 hover:bg-slate-800 text-white",
+ "btn_secondary": "border border-slate-300 text-slate-700 hover:bg-slate-100",
+ "section_alt": "bg-white", "muted": "text-slate-500",
+ "border": "border-slate-200",
+ },
+}
+
+
+# ---------------------------------------------------------------------------
+# TSX generators
+# ---------------------------------------------------------------------------
+
+def tsx_nav(config: Dict[str, Any], style: Dict[str, str]) -> str:
+ brand = config.get("brand", "Brand")
+ nav_links = config.get("nav_links", [])
+ cta = config.get("nav_cta", {"text": "Get Started", "url": "#"})
+ links_jsx = "\n ".join(
+ f'{l.get("text", "")}'
+ for l in nav_links
+ )
+ return f'''function Navbar() {{
+ return (
+
+ );
+}}'''
+
+
+def tsx_hero(hero: Dict[str, Any], style: Dict[str, str]) -> str:
+ h1 = hero.get("headline", "Your Headline Here")
+ sub = hero.get("subheadline", "")
+ primary_cta = hero.get("primary_cta", {"text": "Get Started", "url": "#"})
+ secondary_cta = hero.get("secondary_cta", None)
+ secondary_jsx = ""
+ if secondary_cta:
+ secondary_jsx = f'''
+
+ {secondary_cta.get("text", "Learn More")}
+ '''
+ return f'''function Hero() {{
+ return (
+
+