Communitygithub.com

qike7777/skill-library

Build a stunning, conversion-optimized landing page with a distinctive visual identity.

What is skill-library?

This skill accelerates the creation of high-converting landing pages by integrating the UI-UX Design Pro database, which contains 67+ UI styles, 161 color palettes, 57 font pairings, and 35 landing page patterns. It covers the complete pipeline from design research and copywriting to building responsive HTML/CSS (or Next.js/React), generating live previews, and deploying to Vercel. The skill emphasizes fast, focused execution without heavy engineering workflows, making it ideal for product launches, waitlist pages, and SaaS marketing sites.

Works with✓Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/qike7777/skill-library/tree/HEAD/skills/3-websites-and-apps/landing-page

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

SKILL.md — Landing Page Builder

Build a conversion-optimized landing page with a distinctive visual identity — backed by 67+ UI styles, 161 color palettes, 57 font pairings, and 35 landing page patterns. Ships fast: design research → copy → code → live preview → deploy.


Overview

A landing page has one job: convert visitors into leads, signups, or customers. Everything — design, copy, structure, CTA — serves that one goal.

Pipeline (5 Phases):

Phase 0 — Understand    →  What is this page for? Who is it for? What's the #1 action?
Phase 1 — Design        →  Style, color palette, fonts from the design database
Phase 2 — Copy          →  Headline, subheadline, sections, CTA text
Phase 3 — Build         →  HTML/CSS (default) or Next.js static page
Phase 4 — Deliver       →  Live preview → Vercel deploy

Tech Stack Options

StackWhen to Use
HTML + CSS + Vanilla JSDefault. Fastest to build and deploy. No dependencies.
Next.js (static export)When user already has a Next.js project, or needs MDX/i18n
React + ViteWhen user wants component-based structure but not full Next.js

Default to HTML + CSS + Vanilla JS unless the user specifies otherwise. A landing page doesn't need a framework.

File Structure (HTML default)

landing-page/
├── index.html          # Main page
├── styles.css          # All styles + CSS variables (design tokens)
├── main.js             # Minimal JS: mobile nav toggle, scroll effects, form
├── assets/
│   ├── fonts/          # Self-hosted fonts (if not using Google Fonts CDN)
│   └── images/         # Logo, hero image, etc.
└── README.md

Phase 0 — Understand the Page

0.1 Key Questions

Before any design or copy work, answer these:

QuestionWhy It Matters
What is this page promoting?Product, service, event, waitlist, app, course...
Who is the target visitor?Demographics, pain points, level of awareness
What is the ONE action you want visitors to take?Sign up, buy, download, contact, join waitlist
What's the current stage?Pre-launch (waitlist) / launch / established product
Any existing brand?Colors, fonts, logo — or starting from scratch?
Tone?Professional, playful, bold, minimalist, luxury...
Competitors' pages?Any to emulate or differentiate from?

0.2 Conversion Goal Mapping

Page TypePrimary CTAKey Sections
Waitlist / Pre-launch"Join the waitlist"Hero + Problem + Teaser + Social proof + CTA
SaaS Product"Start free trial" / "Get started"Hero + Problem + Solution + Features + Pricing + FAQ + CTA
Mobile App"Download on App Store"Hero + Screenshots + Features + Reviews + Download
Course / Event"Enroll now" / "Register"Hero + What you'll learn + Instructor + Curriculum + Testimonials + CTA
Agency / Service"Book a call" / "Get a quote"Hero + Services + Process + Case studies + Trust + CTA
Physical Product"Buy now" / "Shop"Hero + Product shots + Benefits + Reviews + FAQ + CTA

Phase 1 — Design Research

1.1 The Design Database

# Style search
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --domain style --max-results 5

# Color palette
python3 src/ui-ux-pro-max/scripts/search.py "<mood/industry>" --domain color --max-results 5

# Typography
python3 src/ui-ux-pro-max/scripts/search.py "<style/mood>" --domain typography --max-results 3

# Landing page patterns (35 templates)
python3 src/ui-ux-pro-max/scripts/search.py "<product type>" --domain landing --max-results 3

# Product-type rules (anti-patterns included)
python3 src/ui-ux-pro-max/scripts/search.py "<product type>" --domain product

# Full design system shortcut
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "<Page Name>"

# Stack-specific snippets
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --stack html
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --stack nextjs

1.2 Anti-AI-Slop Rule

Before touching code, commit to a specific aesthetic direction. Landing pages especially suffer from generic AI aesthetics:

❌ Generic (avoid)✅ Distinctive (aim for)
Purple/blue gradient hero on whiteA palette with real personality and contrast
Inter font everywhereA distinctive heading font that sets the tone
3 icon cards with "Feature 1, 2, 3"Layouts that serve the actual content
Stock photo heroPurposeful imagery or illustration direction
CTA button that looks like every other siteA button that earns attention

1.3 Design Brief for Landing Pages

## Landing Page Design Brief: <Product/Service Name>

### Page Goal
- **What it promotes:** <product/service/event>
- **Primary CTA:** <exact CTA text>
- **Target visitor:** <who>
- **Page type:** <waitlist / SaaS / app / course / agency / product>

### Style Direction
- **Primary style:** <from search — e.g., "Dark Glassmorphism", "Warm Editorial">
- **One-word aesthetic:** <e.g., "urgent", "premium", "playful", "authoritative">
- **Why this style:** <one sentence>

### Color Palette
- **Background:** <hex> — <name>
- **Text primary:** <hex>
- **Accent / CTA color:** <hex> — must be high-contrast, draws the eye
- **Surface / card:** <hex>
- **Gradient (if any):** <from> → <to>

### Typography
- **Heading font:** <name> + Google Fonts URL
- **Body font:** <name> + Google Fonts URL
- **Heading size (hero):** <e.g., 64px desktop / 40px mobile>

### Landing Page Pattern
- **Pattern:** <from landing search results>
- **Section order:** <list>

### Key Effects
- <animations, scroll effects, hover states from style search>

### Anti-Patterns to Avoid
- <from product search>

1.4 Quality Criteria

  • Page type identified, conversion goal clear
  • At least 3 style options searched and considered
  • Color palette: bg, text, accent, surface all defined
  • Accent/CTA color is high-contrast and visually dominant
  • Font pairing selected with Google Fonts links
  • Landing page pattern chosen (section order)
  • User approved the Design Brief

Phase 2 — Copy

2.1 Copy Hierarchy

Every section of a landing page serves a specific persuasion function:

Hero           → Grab attention + communicate core value in 3 seconds
Problem        → Make the visitor feel understood ("you have this pain")
Solution       → Introduce the product as the answer
Features/Benefits → Prove it — show HOW it solves the problem
Social Proof   → Build trust — testimonials, logos, numbers
Pricing        → Remove the decision barrier (if applicable)
FAQ            → Address objections
CTA            → Ask for the action — clear, urgent, low-friction

2.2 Headline Formula

The hero headline must answer: "What is it, who is it for, and why should I care?" in under 10 words.

Strong formulas:

  • [Outcome] for [Audience] — without [Pain]
  • The [adjective] way to [do the thing]
  • [Big promise]. [Short proof].
  • Stop [bad thing]. Start [good thing].

Avoid:

  • Vague value props ("The platform that transforms your workflow")
  • Feature-first headlines ("Built with AI and machine learning")
  • Question headlines ("Tired of X?") — overused

2.3 CTA Copy Rules

❌ Weak✅ Strong
SubmitGet early access
Click hereStart my free trial
Learn moreSee how it works
Sign upJoin 2,400 founders

CTA should state what the visitor gets, not what they do.

2.4 Copy by Page Type

Waitlist page:

  • Headline: The promise of what's coming
  • Subheadline: Who it's for + when
  • Social proof: "X people already on the list"
  • CTA: "Get early access" / "Join the waitlist"

SaaS product:

  • Headline: The outcome the software delivers
  • Features: 3-4, benefit-first (not feature-first)
  • Social proof: customer logos OR testimonials (not both on small pages)
  • Pricing: 3 tiers max, highlight the recommended one

Mobile app:

  • Hero: app screenshots prominently displayed
  • Feature list: 3-5 key things, 1-line each
  • Reviews: 3 star ratings with text
  • Download badges: App Store + Google Play

2.5 Quality Criteria

  • Hero headline answers "what, who, why" in under 10 words
  • Subheadline adds one specific detail the headline can't fit
  • All CTAs state what the visitor gets (not what they do)
  • Features are written as benefits (outcome-first, not feature-first)
  • Social proof is specific (numbers, names, logos — not vague)
  • No filler phrases ("world-class", "cutting-edge", "revolutionize")

Phase 3 — Build

3.1 HTML Structure

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title><Page Title> — <Tagline></title>
  <meta name="description" content="<150-char description>">

  <!-- Google Fonts -->
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link href="https://fonts.googleapis.com/css2?family=<HeadingFont>:wght@400;600;700&family=<BodyFont>:wght@400;500&display=swap" rel="stylesheet">

  <!-- OG Tags for social sharing -->
  <meta property="og:title" content="<title>">
  <meta property="og:description" content="<description>">
  <meta property="og:image" content="<og-image-url>">

  <link rel="stylesheet" href="styles.css">
</head>
<body>
  <!-- Nav -->
  <nav class="nav">...</nav>

  <!-- Hero -->
  <section class="hero">...</section>

  <!-- [Sections per Design Brief pattern] -->

  <!-- Final CTA -->
  <section class="cta-section">...</section>

  <!-- Footer -->
  <footer class="footer">...</footer>

  <script src="main.js"></script>
</body>
</html>

3.2 CSS Architecture

/* ── 1. Google Fonts import (or @font-face) ── */
/* ── 2. CSS Variables (design tokens) ── */
:root {
  /* Colors from Design Brief */
  --color-bg: <hex>;
  --color-bg-secondary: <hex>;
  --color-text: <hex>;
  --color-text-muted: <hex>;
  --color-accent: <hex>;        /* CTA color — high contrast */
  --color-accent-hover: <hex>;
  --color-surface: <hex>;       /* card/panel bg */
  --color-border: <hex>;

  /* Typography */
  --font-heading: '<HeadingFont>', serif;
  --font-body: '<BodyFont>', sans-serif;

  /* Type scale */
  --text-hero: clamp(2.5rem, 6vw, 4.5rem);  /* responsive hero headline */
  --text-h2: clamp(1.75rem, 4vw, 2.75rem);
  --text-h3: clamp(1.25rem, 2.5vw, 1.75rem);
  --text-body: 1.125rem;
  --text-sm: 0.9rem;

  /* Spacing */
  --section-padding: clamp(4rem, 10vw, 8rem);
  --container-width: 1200px;
  --gap: 1.5rem;
  --radius: 12px;
  --radius-lg: 20px;

  /* Shadows */
  --shadow-sm: 0 1px 3px rgba(0,0,0,0.08);
  --shadow-md: 0 4px 16px rgba(0,0,0,0.12);
  --shadow-lg: 0 8px 32px rgba(0,0,0,0.16);
}

/* ── 3. Reset + Base ── */
/* ── 4. Layout utilities (.container, .section, .grid) ── */
/* ── 5. Components (nav, button, card, badge, form) ── */
/* ── 6. Sections (hero, features, pricing, testimonials, cta, footer) ── */
/* ── 7. Animations + effects ── */
/* ── 8. Responsive (mobile-first: min-width breakpoints) ── */

3.3 Key Section Implementations

Hero Section

<section class="hero">
  <div class="container">
    <div class="hero__content">
      <!-- Badge (optional) -->
      <span class="badge">✦ Now in beta</span>

      <!-- Headline — most important element on the page -->
      <h1 class="hero__headline">
        <span class="hero__headline-main"><Main headline></span>
        <span class="hero__headline-accent"><Accented part></span>
      </h1>

      <!-- Subheadline -->
      <p class="hero__subheadline"><Subheadline — 1-2 sentences></p>

      <!-- CTA group -->
      <div class="hero__cta">
        <a href="#signup" class="btn btn--primary btn--lg"><Primary CTA></a>
        <a href="#how-it-works" class="btn btn--ghost"><Secondary CTA></a>
      </div>

      <!-- Social proof micro-signal -->
      <p class="hero__proof"><★★★★★ Trusted by 2,400+ users></p>
    </div>

    <!-- Visual (product screenshot, illustration, etc.) -->
    <div class="hero__visual">
      <div class="hero__visual-wrapper">
        <!-- product screenshot / mockup / illustration -->
      </div>
    </div>
  </div>
</section>

CTA Button System

.btn {
  display: inline-flex;
  align-items: center;
  gap: 0.5rem;
  font-family: var(--font-body);
  font-weight: 600;
  border-radius: var(--radius);
  cursor: pointer;
  transition: all 0.2s ease;
  text-decoration: none;
  border: 2px solid transparent;
}
.btn--primary {
  background: var(--color-accent);
  color: #fff;
  padding: 0.875rem 2rem;
}
.btn--primary:hover {
  background: var(--color-accent-hover);
  transform: translateY(-2px);
  box-shadow: var(--shadow-md);
}
.btn--ghost {
  background: transparent;
  color: var(--color-text);
  border-color: var(--color-border);
  padding: 0.875rem 1.5rem;
}
.btn--lg { font-size: 1.0625rem; padding: 1rem 2.25rem; }
.btn--sm { font-size: 0.875rem; padding: 0.5rem 1.25rem; }

Signup Form (waitlist / lead capture)

<form class="signup-form" id="signup">
  <input
    type="email"
    name="email"
    placeholder="Enter your email"
    required
    autocomplete="email"
    class="signup-form__input"
  >
  <button type="submit" class="btn btn--primary">
    <Primary CTA text>
  </button>
</form>
// main.js — form submission (connect to Formspree / Mailchimp / etc.)
document.querySelector('.signup-form')?.addEventListener('submit', async (e) => {
  e.preventDefault()
  const email = e.target.email.value
  // TODO: connect to form backend (Formspree, ConvertKit, etc.)
  e.target.innerHTML = '<p class="signup-form__success">✓ You\'re on the list!</p>'
})

3.4 Scroll Animations

// Intersection O

…

[truncated for translation]

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

Related Skills