{"skill":{"slug":"solo-landing-gen","displayName":"Landing Gen","summary":"Generate landing page content from PRD — hero section, features, A/B headline variants, CTA, and SEO meta tags. Use when user says \"create landing page\", \"wr...","description":"---\nname: solo-landing-gen\ndescription: Generate landing page content from PRD — hero section, features, A/B headline variants, CTA, and SEO meta tags. Use when user says \"create landing page\", \"write landing copy\", \"hero section\", \"A/B headlines\", or \"landing content\". Can scaffold actual pages for astro-static. Do NOT use for SEO auditing (use /seo-audit).\nlicense: MIT\nmetadata:\n  author: fortunto2\n  version: \"1.1.1\"\n  openclaw:\n    emoji: \"🛬\"\nallowed-tools: Read, Grep, Glob, Write, Edit, Bash, AskUserQuestion, mcp__solograph__kb_search, mcp__solograph__project_info, mcp__solograph__web_search\nargument-hint: \"<project-name>\"\n---\n\n# /landing-gen\n\nGenerate 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.\n\n## MCP Tools (use if available)\n\n- `kb_search(query)` — find related methodology (conversion, copywriting)\n- `project_info(name)` — get project stack and details\n- `web_search(query)` — competitor landing analysis\n\nIf MCP tools are not available, fall back to Glob + Grep + Read.\n\n## Steps\n\n1. **Parse project** from `$ARGUMENTS`.\n   - Read PRD, README, or research.md for product info.\n   - If empty: ask via AskUserQuestion.\n\n2. **Detect stack:**\n   - Check for `astro.config.*` → astro-static (can scaffold page)\n   - Check for `next.config.*` → Next.js (can scaffold route)\n   - Otherwise: generate content-only markdown\n\n3. **Extract landing inputs** from PRD/README:\n   - **Problem:** 1 sentence pain statement\n   - **Solution:** 1 sentence product description\n   - **ICP:** Target user persona\n   - **Features:** Top 3-4 differentiating features with descriptions\n   - **Competitors:** From research.md (if exists) — for positioning\n   - **Pricing:** If available\n\n4. **Competitor landing analysis** (optional, if MCP/WebSearch available):\n   - Search for top 3 competitor landing pages\n   - Note: headline patterns, CTA language, social proof types\n   - Identify positioning gaps\n\n5. **Forced reasoning — conversion strategy:**\n   Before generating, write out:\n   - **Primary conversion:** What's the ONE action? (sign up / download / buy)\n   - **Objections:** Top 3 reasons someone wouldn't convert\n   - **Trust signals:** What overcomes each objection?\n   - **Above the fold:** Problem + Solution + CTA — nothing else\n\n6. **Generate landing content:**\n\n   ### 6a. Hero Section\n   - **Headline:** Problem-focused, benefit-driven (8-12 words)\n   - **Subheadline:** How the product solves it (15-25 words)\n   - **CTA button:** Action verb + outcome (\"Start Free Trial\", \"Download Now\")\n   - **Visual:** Describe what image/screenshot/demo should be shown\n\n   ### 6b. A/B Headline Variants (5 options)\n   Generate 5 distinct headline approaches:\n   1. Pain-focused: \"Tired of {problem}?\"\n   2. Benefit-focused: \"{Outcome} without {hassle}\"\n   3. Curiosity: \"The {adjective} way to {action}\"\n   4. Social proof: \"Join {N}+ {users} who {outcome}\"\n   5. Direct: \"{Product}: {one-line value prop}\"\n\n   ### 6c. Features Section (3-4 features)\n   For each feature:\n   - Icon suggestion (emoji or icon name)\n   - Feature title (3-5 words)\n   - Feature description (1-2 sentences)\n   - Benefit framing (what user gains, not what product does)\n\n   ### 6d. Social Proof Section\n   - Placeholder for testimonials (template with name, role, quote)\n   - Metrics placeholders (\"X+ users\", \"Y% faster\", \"Z countries\")\n   - Trust badges placeholder (App Store rating, awards, press)\n\n   ### 6e. CTA Section\n   - Repeat headline (or variation)\n   - CTA button (same as hero)\n   - Risk reducer (\"Free forever\" / \"No credit card\" / \"Cancel anytime\")\n\n   ### 6f. SEO Meta Tags\n   ```html\n   <title>{title — 50-60 chars}</title>\n   <meta name=\"description\" content=\"{description — 150-160 chars}\">\n   <meta property=\"og:title\" content=\"{og title}\">\n   <meta property=\"og:description\" content=\"{og description}\">\n   <meta property=\"og:image\" content=\"{suggest image dimensions 1200x630}\">\n   <meta property=\"og:type\" content=\"website\">\n   ```\n\n7. **Write output:**\n\n   **If astro-static detected:** scaffold page at `src/pages/index.astro` or new route.\n\n   **Otherwise:** write to `docs/landing-content.md`:\n\n   ```markdown\n   # Landing Page Content: {Project Name}\n\n   **Generated:** {YYYY-MM-DD}\n   **Primary CTA:** {action}\n   **Target ICP:** {persona}\n\n   ## Hero\n   **Headline:** {headline}\n   **Subheadline:** {subheadline}\n   **CTA:** {button text}\n   **Visual:** {description}\n\n   ## A/B Headlines\n   1. {variant 1}\n   2. {variant 2}\n   3. {variant 3}\n   4. {variant 4}\n   5. {variant 5}\n\n   ## Features\n   {features with icons and descriptions}\n\n   ## Social Proof\n   {templates and placeholders}\n\n   ## Final CTA\n   {closing section}\n\n   ## SEO Meta Tags\n   {html meta tags}\n\n   ---\n   *Generated by /landing-gen. Fill in social proof, add visuals, then publish.*\n   ```\n\n8. **Output summary** — headline, CTA, and suggested next steps.\n\n## Notes\n\n- Headline should be testable — run A/B with 2-3 variants\n- \"Above the fold\" = hero only — don't overload\n- Social proof is placeholder — fill with real data as it comes\n- For fake-door tests: hero + CTA + email capture is enough (2-hour launch)\n- Works with /seo-audit — generate content, then audit the deployed page\n\n## Common Issues\n\n### No PRD or product info found\n**Cause:** Project lacks `docs/prd.md` or README with product description.\n**Fix:** Run `/validate` to generate PRD first, or provide a README with problem/solution/features.\n\n### Headlines too generic\n**Cause:** Weak problem statement or missing competitor differentiation.\n**Fix:** Add `research.md` with competitive analysis. Specific pain points produce specific headlines.\n\n### Stack not detected for page scaffolding\n**Cause:** No `astro.config.*` or `next.config.*` found.\n**Fix:** Skill outputs content-only markdown by default. To get actual page files, ensure the project uses astro-static or nextjs-supabase stack.\n","tags":{"latest":"1.1.1"},"stats":{"comments":0,"downloads":1180,"installsAllTime":44,"installsCurrent":0,"stars":0,"versions":2},"createdAt":1771616141735,"updatedAt":1778991939513},"latestVersion":{"version":"1.1.1","createdAt":1771711601043,"changelog":"Universalize: remove project-specific references, add SearXNG recommendation","license":null},"metadata":{"setup":[],"os":null,"systems":null},"owner":{"handle":"fortunto2","userId":"s17ccp4nxta4tm3ahx4kexjbq5885bd3","displayName":"Rust","image":"https://avatars.githubusercontent.com/u/1236751?v=4"},"moderation":null}