本文へ移動
cccskills
無料GitHub で公開

landing-page

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.

インストール方法を見る

含まれるファイル(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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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?

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Build convincing woven cloth in Three.js, with a thread-level weave normal map, sheen and anisotropic highlights, folds that never stretch the texture, hems with thickness, stitches, seams, frayed edges, fold occlusion, dye and wear variation, and light passing through thin fabric. Use for linen, silk, wool, canvas, curtains, banners, cloaks, tablecloths, tapestries or any 3D drape that currently looks like a plastic sheet, a stretched texture, or a flat coloured plane.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

Build recognizable falling leaves in world space using instanced geometry, independent tumble, coupled sideways drift, shared wind, scene occlusion, and camera-aware recycling. Use for 3D autumn leaves or drifting foliage in Three.js and similar scenes; use falling-leaves for a 2D canvas overlay.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

Add coordinated spring, summer, fall, and winter states to a 3D scene, blending foliage, sunlight, sky, ground materials, snow, and particles without rebuilding the world. Use for seasonal controls, architectural walkthroughs, and outdoor scenes with four-season transitions.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

Create or integrate highly detailed 3D models with smooth silhouettes, shaped surfaces, believable bevels, and close-up geometry, then prepare suitable runtime LODs and loading. Use when a user requests high polygon counts, ultra-realistic models, detailed architectural assets, or removal of visibly faceted geometry.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

Build sharp, physically coherent high-resolution materials for 3D rendering with appropriate PBR maps, texel density, UV direction, mipmaps, anisotropic filtering, and progressive asset delivery. Use for detailed wood, stone, fabric, foliage, and architectural close-ups without excessive download or GPU memory costs.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

Build hyperrealistic PBR metal in Three.js: steel, brass, gold, copper and iron as true conductors (metalness 1, measured F0 tint, no albedo) with roughness-varied finishes (polished, brushed anisotropic, aged with patina and worn edges) lit by a dark HDR studio of real bright window cards prefiltered with PMREM. Use when metal looks like grey plastic, a dull blur, or a black hole; when blades, tools, rings, ingots, hardware or product metal need reflections with edges and structure; or when a finish needs scratches, streaks, fingerprints and bevels that catch light.

日本語の概要は準備中です。原文の説明を表示しています。

MengTo/Skills6,7372026年10月6日 更新

MengTo のスキルをすべて見る

このスキルの問題を報告する