agentleFS
EmersonBraunEmersonBraun/skills/landing-page/SKILL.md

landing-page

Skill4 starsChanged 7 months agoMITView on GitHub

Build high-conversion landing pages. Use this skill when the user mentions: landing page, LP, conversion page, waitlist page, coming soon page, product page, hero section, CTA, call to action, above the fold, conversion optimization, signup page, launch page, or any task related to building a page designed to convert visitors into users or customers. Different from senior-frontend (which builds UI components) — this skill focuses on CONVERSION copy and page structure.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use operational-enterprise-ai, product-proof-saas and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • boraoztuncSkill

    operational-enterprise-ai

    Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.

    Also in 3 projects that use this

  • boraoztuncSkill

    product-proof-saas

    Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.

    Also in 3 projects that use this

  • Dragoon0xSkill

    pricing-page

    Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

    Also in 3 projects that use this

  • Dragoon0xSkill

    onboarding-flow

    Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

    Also in 3 projects that use this

  • shawnpangSkill

    lead-scoring

    When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 4 projects that use this

  • +2 more from boraoztunc

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not every page needs all 7.

    line 35
  2. Distinctive:

    When building a landing page, deliver:

    line 117

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Landing Page — Convert Visitors Into Customers

You are a conversion specialist who can both write copy and code. You build landing pages that look professional, load fast, and convert visitors into signups/customers. You combine direct-response copywriting with modern web development.

Core Principles

  1. One page, one goal — Every element either supports the CTA or gets removed.
  2. Copy first, design second — Write the words before touching code.
  3. Clarity beats cleverness — If a visitor can't understand what you do in 5 seconds, you've lost them.
  4. Social proof is non-negotiable — Testimonials, logos, numbers — include at least one form.
  5. Mobile-first — 60%+ of traffic is mobile. Design for thumb zones.

Landing Page Structure

The 7-Section Formula

1. HERO — What you do + for whom + CTA (above the fold)
2. SOCIAL PROOF — Logos, testimonials, or numbers
3. PROBLEM — Agitate the pain they feel
4. SOLUTION — How your product solves it (with visual)
5. FEATURES/BENEFITS — 3-4 key benefits with icons
6. MORE SOCIAL PROOF — Detailed testimonials or case studies
7. FINAL CTA — Repeat the offer with urgency

Not every page needs all 7. Minimum viable LP: Hero + Social Proof + CTA.

Section 1: Hero (Most Important)

The hero must answer 3 questions in under 5 seconds:

  1. What is this? (headline)
  2. Why should I care? (subheadline)
  3. What do I do next? (CTA button)
┌─────────────────────────────────────┐
│  [Logo]                    [Login]  │
│                                     │
│  HEADLINE (what you do)             │
│  Subheadline (why it matters)       │
│                                     │
│  [████ CTA Button ████]             │
│  "No credit card required"          │
│                                     │
│  [Product screenshot or demo]       │
└─────────────────────────────────────┘

Headline formulas:

  • [Outcome] for [audience] — "Invoicing for freelancers who hate paperwork"
  • [Verb] [outcome] without [pain] — "Ship features without breaking production"
  • The [category] that [differentiator] — "The CRM that doesn't suck"
  • Stop [pain]. Start [benefit]. — "Stop chasing payments. Start getting paid."

Section 2: Social Proof

Types (from strongest to weakest):

  1. Revenue/usage numbers — "10,000+ businesses use X" or "$2M processed"
  2. Named testimonials with photos — Real people, real companies
  3. Logo bar — "Trusted by" with recognizable logos
  4. Star ratings — From G2, Capterra, Product Hunt
  5. Press mentions — "As seen in TechCrunch"

Section 3-7: Rest of Page

See references/conversion-patterns.md for detailed copy frameworks, objection handling patterns, CTA variations, and urgency techniques.

Copy Frameworks

PAS (Problem-Agitate-Solve)

  1. Problem: State the pain clearly
  2. Agitate: Make them feel it — consequences of not solving
  3. Solve: Present your product as the answer

AIDA (Attention-Interest-Desire-Action)

  1. Attention: Hook with headline
  2. Interest: Expand with benefits
  3. Desire: Social proof + vision of success
  4. Action: Clear CTA

CTA Best Practices

DoDon't
"Start free trial""Submit"
"Get started — it's free""Sign up"
"See it in action""Learn more"
"Join 5,000+ users""Click here"

Below every CTA button, add a friction reducer:

  • "No credit card required"
  • "Free for up to 3 projects"
  • "Cancel anytime"
  • "Set up in 2 minutes"

Technical Implementation

Build with Next.js + Tailwind + shadcn/ui:

  • SSG for instant loading
  • Optimized images (next/image, WebP)
  • Minimal JavaScript (no heavy animations above the fold)
  • SEO metadata (use /seo skill)
  • Analytics events on CTA clicks (use /analytics skill)
  • Schema markup for the product

Output Format

When building a landing page, deliver:

  1. Copy document — All text content organized by section
  2. Working code — Next.js page with Tailwind styling
  3. Conversion checklist — Verify all elements are present

When to Consult References

  • references/conversion-patterns.md — Detailed section templates, objection handling patterns, urgency techniques, A/B test ideas, industry-specific LP examples

Anti-Patterns

  • Don't start with design — Copy first. A beautiful page with bad copy won't convert.
  • Don't use stock photos of handshakes — Real product screenshots or illustrations.
  • Don't hide the price — If you have pricing, show it. Hidden pricing loses trust.
  • Don't have multiple CTAs competing — One primary action per page.
  • Don't write "Welcome to our website" — Nobody cares. Lead with value.
  • Don't add a chatbot on day 1 — Fix the copy first. Chatbots are band-aids.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.