Skip to content
cccskills
FreePublished on GitHub

landing-page

Plan or rewrite a landing page for a SaaS product, app, or service around one audience and one action. Produce page structure, headlines, benefit copy, FAQs, layout recommendations, and guidance on search visibility.

OriginalShow the original description

Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.

See how to install

Good for

  • Plan a landing page for trial signups
  • Align landing page copy with an ad
  • Address purchase concerns with evidence and FAQs
  • Review search visibility and page metadata

Files included (5)

  • SKILL.md5.2 KB
  • demo/index.html16.1 KB
  • demo/preview.jpg56.4 KB
  • demo/PROMPT.md1.8 KB
  • REFERENCES.md288 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Landing Page (High‑Conversion) — Web Design Skill

A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: one offer → one audience → one primary action.

Before you design/write

Gather (ask if missing):

1) Page purpose

  • What is the ONE primary action? (trial, demo, buy, waitlist, download)
  • What’s the offer? (exactly what do they get?)
  • What counts as conversion? (click, signup, purchase)

2) Audience + context

  • Who is the ICP?
  • What problem are they trying to solve?
  • Top 3 objections (why they don’t convert today)
  • Traffic source: ads / search / social / email
  • What do visitors already know when they land?

3) Proof + assets

  • Any proof points: logos, testimonials, numbers, case studies
  • Screenshots, demo video, product GIFs
  • Guarantees / refund / cancellation terms

4) Constraints

  • Brand voice: casual vs professional
  • Design direction: minimal editorial vs playful 3D vs glass UI
  • Mobile priority?

Core structure (what it should include)

Above the fold (must)

  1. Headline (outcome + audience)
  2. Subheadline (clarifies “how” + adds specificity)
  3. Primary CTA (clear verb + what they get)
  4. One proof signal (logo strip / stat / short testimonial)
  5. Hero visual (product screenshot/video) or a strong illustration

Mid page (argument)

  1. Problem → solution (1 section)
  2. Benefits (3–5, outcome-driven)
  3. How it works (3 steps)
  4. Social proof (testimonials/case study)

Bottom (objection handling)

  1. FAQ (6–12 Q/A)
  2. Risk reversal (trial, cancel anytime, guarantee)
  3. Final CTA (same as top)

Layout types (pick one)

A) Classic hero + sections (most common)

Best when:

  • product is understandable with a hero screenshot

B) Long-form story (sales page)

Best when:

  • you need to educate + overcome skepticism

C) Minimal conversion page

Best when:

  • high-intent traffic (email → known users)
  • short offer (download, waitlist)

D) Comparison landing page

Best when:

  • search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages

High‑conversion strategies (practical)

1) Match message to source

If traffic is from ads:

  • mirror the ad headline in the hero
  • use the same promise and visual tone

2) Make the next step obvious

  • one primary CTA
  • avoid multiple competing CTAs above the fold

3) Write benefit-first

  • Features: what it does
  • Benefits: what that means for them

4) Use specificity

  • ❌ “Save time and streamline”
  • ✅ “Cut your weekly reporting from 4 hours to 15 minutes”

5) Reduce risk

Pick at least one:

  • free trial
  • free plan
  • no credit card
  • cancel anytime
  • money-back guarantee

6) Objection handling is a section, not a footer

  • add FAQ earlier if it’s a high-friction offer
  • put proof right next to the claim it supports

Copywriting templates

Headline formulas

  • “{Outcome} without {pain}”
  • “The {category} for {audience}”
  • “Ship {result} in {time}”

Subheadline rules

  • 1–2 sentences
  • clarify what it is + who it’s for

CTA rules

  • Verb + what they get
  • Avoid weak CTAs: “Learn more”, “Submit”

Examples:

  • “Start free trial”
  • “Book a demo”
  • “Get the checklist”

Benefit bullets

Format:

  • Benefit — proof/detail

Example:

  • Faster iteration — generate 3 layout variants in one click.

Section-by-section workflow (designer-friendly)

Work in this order:

  1. Hero
  2. Benefits
  3. How it works
  4. Proof
  5. FAQ
  6. Final CTA

Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control.


SEO + AEO checklist (when relevant)

When landing pages should NOT be indexed

  • ad-only campaigns
  • highly time-bound offers

Use:

  • noindex (or keep it behind a non-indexed path)

When they SHOULD be indexed

  • evergreen offers
  • search intent matches the promise

Add:

  • clear title + meta
  • internal links from homepage/feature pages
  • FAQ in plain Q/A for AEO

Optional:

  • FAQ schema (if appropriate)

Common pitfalls

  • Too many CTAs above the fold
  • Vague value prop (“streamline”, “optimize”)
  • Big feature list with no outcomes
  • Proof hidden at the bottom
  • Mobile layout breaks readability
  • No clear next step

Output format (when generating a landing page)

Return:

  1. Page outline (sections + order)
  2. Hero copy (headline, subheadline, CTA, proof line)
  3. Benefits section (3–5 bullets)
  4. How it works (3 steps)
  5. FAQ (6–12 Q/A)
  6. SEO/AEO (indexing recommendation + title/meta if indexed)
  7. Layout recommendation (A/B/C/D + why)

Quick questions (if user says “make a landing page”)

  • What’s the ONE primary CTA?
  • Who is the ICP and what’s the main pain?
  • Any proof (numbers/testimonials/logos)?
  • What’s the offer and risk reversal?
  • Where is traffic coming from?

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build woven fabric in Three.js with visible threads, realistic sheen, seams, and thick hems. The skill covers folds that preserve texture proportions, light passing through thin cloth, and variations in dye and wear.

  • Creating backlit curtains
  • Differentiating linen, silk, and wool
  • Adding hems and stitches for close-up views
MengTo/Skills7KUpdated Oct 18, 2026

Build falling leaves in Three.js and similar 3D scenes, with visible front, edge, and back views as they tumble and drift. Coordinate wind, scene depth, camera-aware recycling, and performance checks for a convincing autumn effect.

  • Adding falling autumn leaves to a 3D scene
  • Coordinating leaf tumble, sideways drift, and wind
  • Managing leaves around buildings and camera movement
MengTo/Skills7KUpdated Oct 18, 2026

3d-four-seasons

FreeSummary

Add coordinated seasonal transitions to an existing 3D scene. Blend foliage, lighting, sky, ground, snow, and particles from one shared state while preserving camera controls and interactions, so the same place remains recognizable throughout spring, summer, fall, and winter.

  • Add a four-season selector to an outdoor 3D scene
  • Show seasonal changes in an architectural walkthrough
  • Coordinate foliage, sunlight, sky, and ground appearance
MengTo/Skills7KUpdated Oct 18, 2026

Create or integrate detailed 3D models with smooth outlines and believable edges for close-up views. Prepare lower-detail versions for distant viewing, prioritize loading, and measure rendering costs in the actual scene.

  • Creating a detailed 3D model for close-up views
  • Replacing visibly faceted curves with smoother geometry
  • Preparing detailed architectural assets for rendering
MengTo/Skills7KUpdated Oct 18, 2026

Prepare detailed 3D materials that remain clear in close-up views. The skill guides texture resolution, physically based material maps, surface mapping, filtering, and progressive loading while checking download size and GPU memory use.

  • Prepare wood, stone, and fabric materials for close-up views
  • Fix texture seams, grain direction, and normal map orientation
  • Preserve floor and foliage detail at oblique or distant views
MengTo/Skills7KUpdated Oct 18, 2026

Create realistic metal surfaces in Three.js by combining structured reflections, studio lighting, scratches, fingerprints, and beveled edges. Includes polished, brushed, and aged finishes for objects such as tools, rings, and metal product parts.

  • Fixing metal that looks like gray plastic
  • Creating polished or brushed metal finishes
  • Adding patina and worn edges
MengTo/Skills7KUpdated Oct 18, 2026

See all skills by MengTo

Report a problem with this skill