跳到主要内容

landing-page-optimization 标准

Use when working on landing pages — creation, copywriting, design, optimization, or conversion rate improvement. Covers hero sections, above-the-fold content, value propositions, CTAs, landing page templates, and high-converting page structure. Applies to sales pages, lead capture pages, product pages, and marketing site pages. Use this skill for landing page copy, landing page design, landing page optimization, CTA writing, conversion rate optimization, hero section content, value proposition work, and any page builder or landing page template tasks.

在 GitHub 打开

安装方式

cp -r skills/landing-page-optimization ~/.claude/skills/landing-page-optimization

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 无外部命令依赖
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
触发场景
copywritingdesignoptimizationconversion rate

SKILL.md 正文

来源 manojbajaj95/claude-gtm-plugin@0830a46 · 许可 MIT · 内容未修改

Landing Page Optimization

Workspace Context

Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.

Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.

Build, write, and optimize high-converting landing pages combining proven copy frameworks, the 11-essential-elements structure, and a clear creation workflow.


1. Copy Framework

Gather Before Writing

Collect these inputs before drafting any copy:

  • Product/service name and core value proposition
  • Target audience and their primary pain point
  • Key differentiator vs alternatives
  • Desired visitor action (CTA goal)
  • Available social proof (testimonials, stats, logos)

Choose a Framework

FrameworkWhen to Use
PAS (Problem → Agitate → Solution)Strong pain point, emotional product
AIDA (Attention → Interest → Desire → Action)General purpose, awareness campaigns
StoryBrand (Hero → Guide → Plan → CTA → Success)Brand narrative, relationship-driven sales

Section Copy Guide

Hero — Value prop in ≤10 words; subheadline adds specificity; CTA + 1 trust signal above fold.

Headline formulas:

  • [Achieve outcome] without [pain point]
  • The [adjective] way to [desired result]
  • Stop [bad thing]. Start [good thing].

Problem — Name the pain in the audience's language; 2–3 specific scenarios; emotional, not clinical.

Solution — How the product solves it; 3–5 features written as benefits ("saves 2 hrs/day" not "automated scheduling").

How It Works — 3–4 steps, each with a clear action verb; close with CTA.

Social Proof — Testimonial template: "[Specific result]..." — Name, Title, Company. Aim for 4–6 testimonials; include stats and logos if available.

Pricing — Highlight recommended plan; include guarantee copy; one CTA per plan card.

FAQ — 5–10 objection-handling questions; cover pricing, refunds, technical requirements, comparison to alternatives.

Final CTA — Repeat the primary CTA; add urgency or risk-reversal ("Cancel anytime", "30-day guarantee"); larger and more dramatic than hero CTA.

CTA Copy Rules

  • Start with an action verb
  • Be specific: "Start My Free Trial" > "Submit"
  • First-person phrasing often converts better ("Get My Guide")
  • Avoid: "Click Here", "Learn More", "Submit"

Copy Best Practices

  • Active voice, present tense; benefits before features
  • Specific numbers over vague claims ("saves 2 hours" not "saves time")
  • Short sentences; scannable with headers and bullets
  • Address objections before the reader voices them
  • Multiple CTAs (same action) throughout — not multiple competing actions

2. Design Principles (11 Essential Elements)

Every landing page needs all 11 elements. See references/11-essential-elements.md for full detail on each.

#ElementConversion PurposeDesign Note
1URLSEO slug with keywords—
2Header/LogoBrand trust, navigationSticky with blur-on-scroll
3Hero Title + SubtitleClear value prop, H1 with keywordsDistinctive display font, 4–6rem
4Primary CTAHero conversionContrasting color, micro-interaction on hover
5Social ProofCredibility, reduce hesitationAnimated counts, overlapping avatars
6Images/VideosProduct demonstrationDevice mockups or demo video; no stock photos
7Benefits/FeaturesJustify the purchase3–6 items with icons; benefits-first copy
8TestimonialsPeer validation4–6 with photo + name + role; specific results
9FAQObjection removalAccordion; 5–10 questions
10Final CTASecond conversion chanceFull-width section; urgency elements
11FooterTrust + legalContact info, privacy policy, social links

Aesthetic Direction

Pick ONE direction and execute it consistently:

DirectionFeelSuits
MinimalistClean whitespace, monochromaticPremium SaaS, professional services
Bold/MaximalistRich layers, vivid colorsCreative agencies, consumer brands
Retro-FuturisticGeometric, neon, monospaceDev tools, gaming, tech startups
OrganicSoft shapes, earth tonesWellness, food, sustainability
EditorialStrong type hierarchy, asymmetric gridsMedia, content platforms

Avoid: purple gradients on white (overused AI aesthetic), perfectly symmetric layouts on every section, stock photos of people pointing at laptops, default yellow stars.

Tech Stack (when building)

Next.js 14+ · TypeScript · Tailwind CSS · ShadCN UI

Build order: Design system → SEO metadata → Header → Hero (with animations) → Media → Benefits → Testimonials → FAQ → Final CTA → Footer.

See references/component-examples.md for production-ready ShadCN component implementations.


3. Creation Workflow

Follow this sequence for any landing page project:

Step 1 — Define the Goal

  • Single conversion action (one CTA target)
  • Audience segment this page serves
  • Traffic source (ad, email, organic) — shapes tone and assumed context

Step 2 — Structure First

Use the full 11-element structure. Resist shortcutting: pages missing Social Proof or FAQ consistently underperform.

Step 3 — Write Copy

Apply the Copy Framework (§1). Write hero copy first — if the value prop isn't clear in 10 words, clarify the offer before continuing.

Step 4 — Design

Choose aesthetic direction, define design system (fonts, colors, motion), then build section by section.

Step 5 — Optimize

  • Above the fold: value prop + CTA + one trust signal visible without scrolling
  • Multiple CTAs with identical action (not competing goals)
  • Minimal form fields; reduce every friction point
  • Mobile-first; test on real devices
  • Performance: LCP <2.5s, CLS <0.1, no layout shifts

Step 6 — Launch Checklist

  • [ ] Headline is benefit-focused, specific, ≤10 words
  • [ ] Single primary CTA throughout
  • [ ] Social proof present and specific
  • [ ] Mobile responsive
  • [ ] Page loads <3s
  • [ ] Trust signals visible above fold
  • [ ] FAQ covers top 5 objections
  • [ ] Analytics tracking configured

References

  • references/11-essential-elements.md — Detailed breakdown of each element with implementation guidance and good/bad examples
  • references/component-examples.md — Production-ready ShadCN UI components for Hero, Benefits, Testimonials, FAQ, Final CTA, and Footer sections

质量与来源

所属仓库
manojbajaj95/claude-gtm-plugin
仓库星标
106
最近更新
25 天前
采集时间
今天
commit
0830a46f4cfb
内容指纹
sha256:a8e13ba5681e5dc
文件路径
skills/landing-page-optimization/SKILL.md

同仓库其它 Skill

查看全部 50 个
ab-test-setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see data-and-funnel-analytics.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
ad-campaign-management
Use when creating, managing, or optimizing paid advertising campaigns across any platform. Covers ad copy generation, ad creative strategy, campaign management, and competitive intelligence. Triggers on: ad copy, ad creative, paid ads, paid advertising, Facebook ads, LinkedIn ads, Google ads, Meta ads, ad campaign, ad strategy, ad testing, competitive ads, competitor ads, ad library, ad analysis, ad creative generation, campaign management, ROAS, CPC, CTR. Use this skill whenever the user mentions ads, paid channels, ad campaigns, ad copy, ad performance, or wants to analyze competitor advertising.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
app-store-optimization
Use this skill when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
blog-writing-specialist
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
bootstrap
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
brand-messaging-and-positioning
Comprehensive brand messaging, positioning, and value proposition development using proven frameworks including Peep Laja Message Layers, Osterwalder Value Proposition Canvas, Geoffrey Moore positioning, April Dunford's Five Components, StoryBrand SB7, Andy Raskin Strategic Narrative, and Messaging House. Use when developing brand identity, brand messaging architecture, positioning statements, value propositions, messaging hierarchies, brand pillars, taglines, one-liners, elevator pitches, brand guidelines, visual identity systems, or creating Positioning & Messaging Packs. Triggers include: messaging framework, brand positioning, value prop, messaging architecture, brand pillars, brand identity, StoryBrand, positioning statement, brand guidelines, design system, messaging house, corporate identity, brand voice, visual standards.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI