solo-landing-gen

# /landing-gen 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. ## MCP Tools (use if available) - `kb_search(query)` — find related methodology (conversion, copywriting) - `project_info(name)` — get project stack and details - `web_search(query)` — competitor landing analysis If MCP tools are not available, fall back to Glob + Grep + Read. ## Steps 1. **Parse project** from `$ARGUMENTS`. - Read PRD, README, or research.md for product info. - If empty: ask via AskUserQuestion. 2. **Detect stack:** - Check for `astro.config.*` → astro-static (can scaffold page) - Check for `next.config.*` → Next.js (can scaffold route) - Otherwise: generate content-only markdown 3. **Extract landing inputs** from PRD/README: - **Problem:** 1 sentence pain statement - **Solution:** 1 sentence product description - **ICP:** Target user persona - **Features:** Top 3-4 differentiating features with descriptions - **Competitors:** From research.md (if exists) — for positioning - **Pricing:** If available 4. **Competitor landing analysis** (optional, if MCP/WebSearch available): - Search for top 3 competitor landing pages - Note: headline patterns, CTA language, social proof types - Identify positioning gaps 5. **Forced reasoning — conversion strategy:** Before generating, write out: -...