Surge landing

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/surge-landing

Use when asked to design growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures. Examples: "growth-optimized landing", "activation funnel layout", "A/B testable page"From its SKILL.md

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill surge-landing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 572 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 1 file

277 B alongside SKILL.md

.claude-plugin/

plugin.json277 B