hero-generator

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill hero-generator
0 commentsdiscussion
summary

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.

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.

Layout Structure Best for
Split (50/50) Text left, visual right (or vice versa); equal weight Product, SaaS; clear value + demo
Split (75/25) Text dominant; smaller image column Copy-heavy; trust-first
Split (25/75 "Signpost") Small image beside primary content Minimal visual; emphasis on headline
Centered Text + CTA centered; visual full-width or stacked Brand, landing; single CTA
Full-width image Image background; overlay text Emotional; 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

Axis Options Use
Horizontal Left, center, right Left align for text-heavy; center for minimal
Vertical Top, center, bottom Center 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

Requirement Practice
Contrast Text over images: >=4.5:1; use overlay if needed
Touch targets CTA >=44x44px
Keyboard CTA keyboard-accessible; visible focus indicator
Screen readers Proper heading order; image alt text; aria-label for icon-only buttons
Reduced motion Respect prefers-reduced-motion for animations
Interaction CTA 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
how to use hero-generator

How to use hero-generator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add hero-generator
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill hero-generator

The skills CLI fetches hero-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/hero-generator

Reload or restart Cursor to activate hero-generator. Access the skill through slash commands (e.g., /hero-generator) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.744 reviews
  • Liam Mensah· Dec 20, 2024

    We added hero-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Xiao Li· Dec 20, 2024

    hero-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ganesh Mohane· Dec 12, 2024

    hero-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Emma Farah· Nov 27, 2024

    hero-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Min Johnson· Nov 11, 2024

    Keeps context tight: hero-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Min Srinivasan· Nov 11, 2024

    hero-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Rahul Santra· Nov 3, 2024

    I recommend hero-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Pratham Ware· Oct 22, 2024

    Useful defaults in hero-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Liam Rahman· Oct 18, 2024

    Solid pick for teams standardizing on skills: hero-generator is focused, and the summary matches what you get after install.

  • Mia Ghosh· Oct 2, 2024

    hero-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 44

1 / 5