본문으로 건너뛰기
cccskills
무료GitHub에 공개

landing-page-generator

Turn a product description into a landing page with headlines, feature sections, pricing, FAQs, and calls to action. Receive Next.js/React components styled with Tailwind CSS, plus search metadata, structured data, and alternative copy.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Generates high-converting landing pages as complete Next.js/React (TSX) components with Tailwind CSS. Creates hero sections, feature grids, pricing tables, FAQ accordions, testimonial blocks, and CTA sections using proven copy frameworks (PAS, AIDA, BAB). Outputs SEO meta tags, structured data, and performance-optimised code targeting Core Web Vitals (LCP under 1s, CLS under 0.1). Use when the user asks to create a landing page, marketing page, homepage, single-page site, lead capture page, campaign page, promo page, or conversion-optimised web page — or when they want to A/B test landing page variants or replace a static page with one designed to convert.

설치 방법 보기

이럴 때 유용합니다

  • Creating a landing page for a new product
  • Building a campaign or lead capture page
  • Comparing headline and page variants
  • Matching a page to an existing brand voice

포함된 파일(6)

  • SKILL.md10.4 KB
  • references/conversion-patterns.md6.0 KB
  • references/copy-frameworks.md7.5 KB
  • references/landing-page-patterns.md2.7 KB
  • references/seo-checklist.md5.0 KB
  • scripts/landing_page_scaffolder.py24.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Landing Page Generator

Generate high-converting landing pages from a product description. Output complete Next.js/React components with multiple section variants, proven copy frameworks, SEO optimization, and performance-first patterns. Not lorem ipsum — actual copy that converts.

Target: LCP < 1s · CLS < 0.1 · FID < 100ms
Output: TSX components + Tailwind styles + SEO meta + copy variants


Core Capabilities

  • 5 hero section variants (centered, split, gradient, video-bg, minimal)
  • Feature sections (grid, alternating, cards with icons)
  • Pricing tables (2–4 tiers with feature lists and toggle)
  • FAQ accordion with schema markup
  • Testimonials (grid, carousel, single-quote)
  • CTA sections (banner, full-page, inline)
  • Footer (simple, mega, minimal)
  • 4 design styles with Tailwind class sets

Generation Workflow

Follow these steps in order for every landing page request:

  1. Gather inputs — collect product name, tagline, audience, pain point, key benefit, pricing tiers, design style, and copy framework using the trigger format below. Ask only for missing fields.
  2. Analyze brand voice (recommended) — if the user has existing brand content (website copy, blog posts, marketing materials), run it through marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py to get a voice profile (formality, tone, perspective). Use the profile to inform design style and copy framework selection:
    • formal + professional → enterprise style, AIDA framework
    • casual + friendly → bold-startup style, BAB framework
    • professional + authoritative → dark-saas style, PAS framework
    • casual + conversational → clean-minimal style, BAB framework
  3. Select design style — map the user's choice (or infer from brand voice analysis) to one of the four Tailwind class sets in the Design Style Reference.
  4. Apply copy framework — write all headline and body copy using the chosen framework (PAS / AIDA / BAB) before generating components. Match the voice profile's formality and tone throughout.
  5. Generate sections in order — Hero → Features → Pricing → FAQ → Testimonials → CTA → Footer. Skip sections not relevant to the product.
  6. Validate against SEO checklist — run through every item in the SEO Checklist before outputting final code. Fix any gaps inline.
  7. Output final components — deliver complete, copy-paste-ready TSX files with all Tailwind classes, SEO meta, and structured data included.

Triggering This Skill

Product: [name]
Tagline: [one sentence value prop]
Target audience: [who they are]
Key pain point: [what problem you solve]
Key benefit: [primary outcome]
Pricing tiers: [free/pro/enterprise or describe]
Design style: dark-saas | clean-minimal | bold-startup | enterprise
Copy framework: PAS | AIDA | BAB

Design Style Reference

StyleBackgroundAccentCardsCTA Button
Dark SaaSbg-gray-950 text-whiteviolet-500/400bg-gray-900 border border-gray-800bg-violet-600 hover:bg-violet-500
Clean Minimalbg-white text-gray-900blue-600bg-gray-50 border border-gray-200 rounded-2xlbg-blue-600 hover:bg-blue-700
Bold Startupbg-white text-gray-900orange-500shadow-xl rounded-3xlbg-orange-500 hover:bg-orange-600 text-white
Enterprisebg-slate-50 text-slate-900slate-700bg-white border border-slate-200 shadow-smbg-slate-900 hover:bg-slate-800 text-white

Bold Startup headings: add font-black tracking-tight to all <h1>/<h2> elements.


Copy Frameworks

PAS (Problem → Agitate → Solution)

  • H1: Painful state they're in
  • Sub: What happens if they don't fix it
  • CTA: What you offer
  • Example — H1: "Your team wastes 3 hours a day on manual reporting" / Sub: "Every hour spent on spreadsheets is an hour not closing deals. Your competitors are already automated." / CTA: "Automate your reports in 10 minutes →"

AIDA (Attention → Interest → Desire → Action)

  • H1: Bold attention-grabbing statement → Sub: Interesting fact or benefit → Features: Desire-building proof points → CTA: Clear action

BAB (Before → After → Bridge)

  • H1: "[Before state] → [After state]" → Sub: "Here's how [product] bridges the gap" → Features: How it works (the bridge)

Representative Component: Hero (Centered Gradient — Dark SaaS)

Use this as the structural template for all hero variants. Swap layout classes, gradient direction, and image placement for split, video-bg, and minimal variants.

export function HeroCentered() {
  return (
    <section className="relative flex min-h-screen flex-col items-center justify-center overflow-hidden bg-gray-950 px-4 text-center">
      <div className="absolute inset-0 bg-gradient-to-b from-violet-900/20 to-transparent" />
      <div className="pointer-events-none absolute -top-40 left-1/2 h-[600px] w-[600px] -translate-x-1/2 rounded-full bg-violet-600/20 blur-3xl" />
      <div className="relative z-10 max-w-4xl">
        <div className="mb-6 inline-flex items-center gap-2 rounded-full border border-violet-500/30 bg-violet-500/10 px-4 py-1.5 text-sm text-violet-300">
          <span className="h-1.5 w-1.5 rounded-full bg-violet-400" />
          Now in public beta
        </div>
        <h1 className="mb-6 text-5xl font-bold tracking-tight text-white md:text-7xl">
          Ship faster.<br />
          <span className="bg-gradient-to-r from-violet-400 to-pink-400 bg-clip-text text-transparent">
            Break less.
          </span>
        </h1>
        <p className="mx-auto mb-10 max-w-2xl text-xl text-gray-400">
          The deployment platform that catches errors before your users do.
          Zero config. Instant rollbacks. Real-time monitoring.
        </p>
        <div className="flex flex-col items-center gap-4 sm:flex-row sm:justify-center">
          <Button size="lg" className="bg-violet-600 text-white hover:bg-violet-500 px-8">
            Start free trial
          </Button>
          <Button size="lg" variant="outline" className="border-gray-700 text-gray-300">
            See how it works →
          </Button>
        </div>
        <p className="mt-4 text-sm text-gray-500">No credit card required · 14-day free trial</p>
      </div>
    </section>
  )
}

Other Section Patterns

Feature Section (Alternating)

Map over a features array with { title, description, image, badge }. Toggle layout direction with i % 2 === 1 ? "lg:flex-row-reverse" : "". Use <Image> with explicit width/height and rounded-2xl shadow-xl. Wrap in <section className="py-24"> with max-w-6xl container.

Pricing Table

Map over a plans array with { name, price, description, features[], cta, highlighted }. Highlighted plan gets border-2 border-violet-500 bg-violet-950/50 ring-4 ring-violet-500/20; others get border border-gray-800 bg-gray-900. Render null price as "Custom". Use <Check> icon per feature row. Layout: grid gap-8 lg:grid-cols-3.

FAQ with Schema Markup

Inject FAQPage JSON-LD via <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }} /> inside the section. Map FAQs with { q, a } into shadcn <Accordion> with type="single" collapsible. Container: max-w-3xl.

Testimonials, CTA, Footer

  • Testimonials: Grid (grid-cols-1 md:grid-cols-3) or single-quote hero block with avatar, name, role, and quote text.
  • CTA Banner: Full-width section with headline, subhead, and two buttons (primary + ghost). Add trust signals (money-back guarantee, logo strip) immediately below.
  • Footer: Logo + nav columns + social links + legal. Use border-t border-gray-800 separator.

SEO Checklist

  • <title> tag: primary keyword + brand (50–60 chars)
  • Meta description: benefit + CTA (150–160 chars)
  • OG image: 1200×630px with product name and tagline
  • H1: one per page, includes primary keyword
  • Structured data: FAQPage, Product, or Organization schema
  • Canonical URL set
  • Image alt text on all <Image> components
  • robots.txt and sitemap.xml configured
  • Core Web Vitals: LCP < 1s, CLS < 0.1
  • Mobile viewport meta tag present
  • Internal linking to pricing and docs

Validation step: Before outputting final code, verify every checklist item above is satisfied. Fix any gaps inline — do not skip items.


Performance Targets

MetricTargetTechnique
LCP< 1sPreload hero image, use priority on Next/Image
CLS< 0.1Set explicit width/height on all images
FID/INP< 100msDefer non-critical JS, use loading="lazy"
TTFB< 200msUse ISR or static generation for landing pages
Bundle< 100KB JSAudit with @next/bundle-analyzer

Common Pitfalls

  • Hero image not preloaded — add priority prop to first <Image>
  • Missing mobile breakpoints — always design mobile-first with sm: prefixes
  • CTA copy too vague — "Get started" beats "Learn more"; "Start free trial" beats "Sign up"
  • Pricing page missing trust signals — add money-back guarantee and testimonials near CTA
  • No above-the-fold CTA on mobile — ensure button is visible without scrolling on 375px viewport

Related Skills

  • Brand Voice Analyzer (marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py) — Run before generation to establish voice profile and ensure copy consistency
  • UI Design System (product-team/ui-design-system/) — Generate design tokens from brand color before building the page
  • Competitive Teardown (product-team/competitive-teardown/) — Competitive positioning informs landing page messaging and differentiation

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

aeo

무료

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

alirezarezvani의 스킬 모두 보기

이 스킬의 문제 신고