From solo
Generates landing page content from PRD: hero section, features, social proof, CTAs, SEO meta tags, A/B headlines. Scaffolds pages for Astro or Next.js stacks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/solo:landing-genThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate landing page content from a project's PRD. Produces hero section, features, social proof, CTA, SEO meta tags, and A/B headline variants. If astro-static stack detected, can scaffold actual page files.
Generate landing page content from a project's PRD. Produces hero section, features, social proof, CTA, SEO meta tags, and A/B headline variants. If astro-static stack detected, can scaffold actual page files.
kb_search(query) — find related methodology (conversion, copywriting)project_info(name) — get project stack and detailsweb_search(query) — competitor landing analysisIf MCP tools are not available, fall back to Glob + Grep + Read.
Parse project from $ARGUMENTS.
Detect stack:
astro.config.* → astro-static (can scaffold page)next.config.* → Next.js (can scaffold route)Extract landing inputs from PRD/README:
Competitor landing analysis (optional, if MCP/WebSearch available):
Forced reasoning — conversion strategy: Before generating, write out:
Generate landing content:
Generate 5 distinct headline approaches:
For each feature:
<title>{title — 50-60 chars}</title>
<meta name="description" content="{description — 150-160 chars}">
<meta property="og:title" content="{og title}">
<meta property="og:description" content="{og description}">
<meta property="og:image" content="{suggest image dimensions 1200x630}">
<meta property="og:type" content="website">
Write output:
If astro-static detected: scaffold page at src/pages/index.astro or new route.
Otherwise: write to docs/landing-content.md:
# Landing Page Content: {Project Name}
**Generated:** {YYYY-MM-DD}
**Primary CTA:** {action}
**Target ICP:** {persona}
## Hero
**Headline:** {headline}
**Subheadline:** {subheadline}
**CTA:** {button text}
**Visual:** {description}
## A/B Headlines
1. {variant 1}
2. {variant 2}
3. {variant 3}
4. {variant 4}
5. {variant 5}
## Features
{features with icons and descriptions}
## Social Proof
{templates and placeholders}
## Final CTA
{closing section}
## SEO Meta Tags
{html meta tags}
---
*Generated by /landing-gen. Fill in social proof, add visuals, then publish.*
Output summary — headline, CTA, and suggested next steps.
og:image, links shared on Twitter/LinkedIn/Slack show a blank preview. Use 1200x630px. Test with https://cards-dev.twitter.com/validator.Cause: Project lacks docs/prd.md or README with product description.
Fix: Run /validate to generate PRD first, or provide a README with problem/solution/features.
Cause: Weak problem statement or missing competitor differentiation.
Fix: Add research.md with competitive analysis. Specific pain points produce specific headlines.
Cause: No astro.config.* or next.config.* found.
Fix: Skill outputs content-only markdown by default. To get actual page files, ensure the project uses astro-static or nextjs-supabase stack.
npx claudepluginhub fortunto2/solo-factory --plugin soloGenerates landing page structures and copy including hero headlines, subheadlines, CTAs, how-it-works steps, features, and buyer psychology elements for sales pages.
Generates high-converting Next.js/React landing pages with Tailwind CSS using PAS, AIDA, and BAB copy frameworks. Outputs complete TSX components (Heroes, Features, Pricing, FAQ, Testimonials, CTA, Footer) with SEO meta and Core Web Vitals optimization.
Designs and builds high-converting landing pages for product launches with hero sections, SEO, waitlists, urgency mechanics, and developer-first patterns. Useful for launch, feature, signup, or marketing pages.