surge-landing — Growth-Optimized Landing Page
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
When to use
User needs a landing page designed for growth: activation funnels, A/B testing, acquisition, or PLG flows.
Workflow
- Identify product type and growth goal from user request (acquisition, activation, PLG, trial, freemium, etc.)
- Search landing page patterns:
python3 -m surge_agent.uiux search --domain landing --query "{product_type}" --limit 3
- Search product reasoning:
python3 -m surge_agent.uiux search --domain product --query "{product_type}" --limit 3
- Search UX for friction points:
python3 -m surge_agent.uiux search --domain ux --query "forms validation loading" --limit 3
- Output experiment-friendly structure with activation triggers and friction audit
Output format
┌─ Growth Landing Page — {product_type} ──────────────────────────────┐
│ # │ Section │ Purpose │ Experiment? │
├────┼────────────────────┼────────────────────────────┼───────────────┤
│ 1 │ {section_name} │ {purpose} │ A/B headline │
│ 2 │ {section_name} │ {purpose} │ — │
│ 3 │ {section_name} │ {purpose} │ A/B CTA copy │
│ … │ … │ … │ … │
└────┴────────────────────┴────────────────────────────┴───────────────┘
Activation triggers: {activation_triggers}
Funnel structure: {funnel_structure}
Friction points: {friction_points}
Experiment surfaces: {experiment_surfaces}
Anti-patterns
- Never optimize for vanity metrics (page views, time on page) over activation metrics
- Never add friction (sign-up gates, long forms) before demonstrating product value
- Never design sections that can't be independently A/B tested
- Never ship a growth page without identifying at least one experiment surface
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
1---2name: surge-landing3description: |4 Use when asked to design growth-optimized landing pages, activation funnel5 layouts, or experiment-friendly page structures. Examples: "growth-optimized6 landing", "activation funnel layout", "A/B testable page"7allowed-tools: Read, Bash, Glob, Grep8version: 0.6.69author: tonone-ai <hello@tonone.ai>10license: MIT11compatibility: Designed for Claude Code12tags: [product, growth, landing]13metadata:14 source: https://skillmd.com/skills/tonone-ai/surge-landing15---1617<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->1819# surge-landing — Growth-Optimized Landing Page2021Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.2223## When to use2425User needs a landing page designed for growth: activation funnels, A/B testing, acquisition, or PLG flows.2627## Workflow28291. **Identify product type and growth goal** from user request (acquisition, activation, PLG, trial, freemium, etc.)302. **Search landing page patterns:**31 ```bash32 python3 -m surge_agent.uiux search --domain landing --query "{product_type}" --limit 333 ```343. **Search product reasoning:**35 ```bash36 python3 -m surge_agent.uiux search --domain product --query "{product_type}" --limit 337 ```384. **Search UX for friction points:**39 ```bash40 python3 -m surge_agent.uiux search --domain ux --query "forms validation loading" --limit 341 ```425. **Output** experiment-friendly structure with activation triggers and friction audit4344## Output format4546```47┌─ Growth Landing Page — {product_type} ──────────────────────────────┐48│ # │ Section │ Purpose │ Experiment? │49├────┼────────────────────┼────────────────────────────┼───────────────┤50│ 1 │ {section_name} │ {purpose} │ A/B headline │51│ 2 │ {section_name} │ {purpose} │ — │52│ 3 │ {section_name} │ {purpose} │ A/B CTA copy │53│ … │ … │ … │ … │54└────┴────────────────────┴────────────────────────────┴───────────────┘5556Activation triggers: {activation_triggers}57Funnel structure: {funnel_structure}58Friction points: {friction_points}59Experiment surfaces: {experiment_surfaces}60```6162## Anti-patterns6364- Never optimize for vanity metrics (page views, time on page) over activation metrics65- Never add friction (sign-up gates, long forms) before demonstrating product value66- Never design sections that can't be independently A/B tested67- Never ship a growth page without identifying at least one experiment surface6869## Delivery7071If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.