landing-page-generator

Generate B2B landing pages from positioning context via a four-phase pipeline.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/FunnelEnvy/funnelenvy-skills --skill landing-page-generator-funnelenvy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-page-generator
Source: https://github.com/FunnelEnvy/funnelenvy-skills/tree/main/skills/landing-page-generator
Command: npx skills add https://github.com/FunnelEnvy/funnelenvy-skills --skill landing-page-generator-funnelenvy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams can generate consistent B2B landing pages from existing positioning context, reducing manual copywriting, design handoffs, and iteration cycles.

Core Features & Use Cases

  • Four-phase LP pipeline: Brief Builder, Copy Agent, Design Agent, QA Validator that consumes context from .claude/context and delivers to .claude/deliverables.
  • Context-driven section catalog: composes sections from persona data, proof points, and brand tokens.
  • One-click deployment: outputs in .claude/deliverables/campaigns/<slug>/ with HTML deliverables page.html and QA reports.
  • Optional brand components: uses brand design system if present for consistent visuals.

Quick Start

Run the command to generate a complete LP: /landing-page-generator <company> <campaign-slug> --stage all.

Frequently Asked Questions about landing-page-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a B2B landing page from existing positioning context?

Generating a B2B landing page from positioning context requires a four-phase pipeline: brief building, copy generation, design rendering, and QA validation. The process reads context files to apply section taxonomy and brand tokens, outputting final HTML deliverables.

What is the best way to automate landing page copy and design without manual handoffs?

Automating landing page copy and design without manual handoffs is achieved using a context-driven pipeline that consumes positioning data to generate sections. This enforces brand alignment and consistency across deliverables, reducing manual iteration cycles.

Do I need a brand design system to generate landing pages with this pipeline?

You do not need a brand design system to generate landing pages, as the pipeline applies default section taxonomy and brand tokens. It optionally uses brand components if present to ensure consistent visuals across campaign deliverables.

How does the landing page generator enforce QA and brand consistency?

The landing page generator enforces QA and brand consistency through a dedicated validation phase that checks copy and design against proof requirements. It automatically applies brand tokens and section taxonomy to maintain alignment across all outputs.

Can I use positioning context files to create campaign deliverables in HTML?

Yes, you can use positioning context files to create campaign deliverables in HTML. The pipeline reads context files to generate the landing page experience and renders final output as an HTML file alongside QA reports in the campaigns directory.