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

hero-generator

When the user wants to design, optimize, or audit hero sections (above-the-fold main visual area). Also use when the user mentions "hero," "hero section," "hero area," "above the fold," "above the fold content," "landing hero," "main banner," "banner section," "first fold," "hero section design," "hero conversion," "split layout hero," "centered hero," or "hero alignment." For homepage, use homepage-generator.

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

dalroot/agentic-seo스타 25(GitHub 25 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.8 KB

SKILL.md(원문)

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

Components: Hero Section

Guides hero section design for conversion and first impressions. The hero is where users spend ~80% of initial viewing time; first impressions form in milliseconds.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for value proposition, audience, and Section 12 (Visual Identity).

Identify:

  1. Page type: Homepage, landing, product, pricing
  2. Primary goal: Signup, trial, purchase, learn more
  3. Platform: Web, mobile, both

Core Components (Four Essentials)

  • Headline (H1): 6–10 words max; instantly communicate core value and benefit. Answer "What's in it for me?" within seconds.
  • Subheading: Clear, concise explanation reinforcing why the product/service is valuable.
  • Primary CTA: Single, prominent action button visible without scrolling. One per hero to avoid choice overload.
  • Visual: High-quality image, video, or animation that amplifies the message.

Optional but Effective

  • Trust cues: 1–3 elements (reviews, logos, statistics)
  • Secondary CTA: For users not ready for primary action

Layout Types

Hero is a Spotlight layout—single focus, primary element with secondary around it. Choose layout by content balance and conversion goal.

LayoutStructureBest for
Split (50/50)Text left, visual right (or vice versa); equal weightProduct, SaaS; clear value + demo
Split (75/25)Text dominant; smaller image columnCopy-heavy; trust-first
Split (25/75 "Signpost")Small image beside primary contentMinimal visual; emphasis on headline
CenteredText + CTA centered; visual full-width or stackedBrand, landing; single CTA
Full-width imageImage background; overlay textEmotional; lifestyle, brand

Responsive: Split layouts stack vertically on mobile (text above image); centered maintains center. Mobile-first; ensure CTA above fold on small screens.

Alignment

AxisOptionsUse
HorizontalLeft, center, rightLeft align for text-heavy; center for minimal
VerticalTop, center, bottomCenter for full-viewport hero; top for short hero

Best Practices

3-Second Rule

The hero must answer three questions within 3 seconds: What is this? Why should I care? What should I do next? ~80% of users never scroll beyond the hero; make an immediate impact.

Messaging

  • No guessing required; message must be instantly clear.
  • Single primary CTA to avoid choice overload.
  • Action-oriented, benefit-focused copy.
  • Emotional intent first: Evoke emotion (trust, excitement, confidence) before users read the headline. Avoid generic phrases ("Welcome to Our Website") or overly clever wordplay.

Visuals

  • Fast-loading; avoid heavy assets that delay LCP
  • Brand-aligned; use typography and colors from brand-visual-generator
  • Support the message; don't distract
  • Frontend aesthetics: For motion (staggered reveals, hover), spatial composition, and backgrounds—see brand-visual-generator Frontend Aesthetics

Technical

  • Mobile-first design
  • Lightweight for quick loading
  • Ensure LCP (Largest Contentful Paint) optimization

SEO Considerations

  • Headline often contains <h1>; include primary keyword
  • Hero content in initial HTML; avoid JS-only rendering. See rendering-strategies
  • Image optimization: Alt text, format (WebP), LCP, responsive—see image-optimization

UX Guidelines

Hierarchy

  • Headline > Subheading > CTA
  • Visual should complement, not compete with, text

Accessibility

RequirementPractice
ContrastText over images: >=4.5:1; use overlay if needed
Touch targetsCTA >=44x44px
KeyboardCTA keyboard-accessible; visible focus indicator
Screen readersProper heading order; image alt text; aria-label for icon-only buttons
Reduced motionRespect prefers-reduced-motion for animations
InteractionCTA has cursor-pointer; hover uses color/opacity (not scale) to avoid layout shift

Testing

  • A/B test headline, CTA copy, and visuals
  • Measure bounce rate, conversion rate, time to first interaction

Output Format

  • Hero structure (headline, subheading, CTA, visual)
  • Copy suggestions
  • Technical checklist (LCP, accessibility, image optimization)
  • Testing recommendations

Related Skills

  • card: Hero vs card—hero is single above-fold; cards are repeated units in grid
  • grid: Hero is one section; content below often uses grid (products, features)
  • cta-generator: Hero typically contains primary CTA
  • trust-badges-generator: Trust cues in hero
  • logo-generator: Logo appears in hero context
  • brand-visual-generator: Typography, colors, spacing for hero design
  • homepage-generator: Hero is central to homepage design
  • landing-page-generator: Hero is step 1 of landing page flow; campaign pages
  • image-optimization: Hero image optimization (alt, WebP, LCP, responsive)
  • rendering-strategies: Content in initial HTML; SSR/SSG for hero

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.

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

dalroot/agentic-seo252026년 10월 20일 업데이트

dalroot의 스킬 모두 보기

이 스킬의 문제 신고