homepage-generator▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides homepage content, structure, and conversion optimization.
Pages: Homepage
Guides homepage content, structure, and conversion optimization.
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.
Homepage Role & Purpose
| Role | Priority | Notes |
|---|---|---|
| Conversion | Primary | Homepage is a trust machine and conversion engine—not a sales pitch. Most visitors (70–80%) are first-time; they need clarity, credibility, and orientation within 3–5 seconds. Convert through trust-building and guided exploration, not aggressive selling. |
| Brand | Primary | First impression, credibility test, orientation center. Answers: Who are you? What do you offer? Why should I care? Brand voice and differentiation live here—see branding. |
| Branded keywords SEO | Required | Primary SEO goal: rank for brand name so people can find you in SERPs. Branded searches indicate high intent and familiarity; they convert better than non-branded. |
| Broad/non-branded SEO | Secondary | Homepage is not the main SEO traffic driver—blog, product pages, and category pages typically carry that. A well-optimized homepage can rank for related non-branded terms as a bonus; do not sacrifice UX or conversion for broad keyword stuffing. |
Principle: SEO and CRO work together. Good homepage SEO aligns with user needs; conversion optimization ensures attracted traffic converts. See landing-page-generator for single-goal campaign pages (homepage is multi-purpose).
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and value proposition. See branding for brand strategy, positioning, differentiation.
Identify:
- Primary goal: Sign up, demo, purchase, learn more
- Audience: Cold visitors, returning, specific segment
- Traffic source: Organic, paid, referral
Homepage Structure
| Section | Purpose |
|---|---|
| Hero | Value proposition, primary CTA, above the fold |
| Social proof | Logos, testimonials, metrics; "As Seen In" (press coverage) when applicable; see customer-stories-page-generator for case study snippets |
| Features/Benefits | What it does, why it matters |
| Use cases | Who it's for, how they use it |
| Objection handling | FAQ, guarantees, comparisons |
| Final CTA | Repeat primary action |
Common Modules (from website-structure)
Combine as needed: Headline, Subheadline, Primary CTA, Supporting Image/Demo, Benefits Section, Social Proof, Search Box (if applicable), Secondary CTA, Banner. Navigation: Horizontal Bar, Dropdown, Hamburger (mobile), Sidebar, Footer; ensure Desktop + Mobile parity. See hero-generator for hero design.
Best Practices
Value Proposition
- Clarity: Visitor understands in 5 seconds
- Specificity: Concrete benefit, not vague
- Differentiation: Why you, not alternatives — see branding for positioning framework
- Customer language: Their words, not jargon
- Avoid "not speaking human": Don't over-emphasize brand with vague definitions; communicate in user-friendly ways—if someone searches "AI presentation maker," the answer should be obvious from your headline
CTA
- One clear primary action (avoid decision paralysis)
- Button copy: value-focused ("Start Free Trial") not generic ("Submit")
- Visible without scrolling
- Repeated at logical points
Conversion Checklist
- Clear value proposition above the fold
- Single primary CTA; simplified navigation (5–7 menu items)
- Immediate social proof (reviews, trust badges, media logos)
- Mobile-first, fast-loading design
Visual & Aesthetics
- Frontend aesthetics: For distinctive typography, motion, spatial composition, backgrounds—see brand-visual-generator Frontend Aesthetics
SEO
Branded keywords first: Title and meta should include brand name; ensure homepage ranks for "[Brand Name]" so users can find the official site. See brand-protection when impersonation risk exists—place "Official website: [domain]" above fold or in hero.
- Title tag (50–60 chars): Brand name + primary keyword; e.g. "Canva – Free Website Builder"
- Meta description (150–160 chars): CTA + secondary keywords; engaging to encourage clicks
- H1: Value proposition or primary headline; one per page; include primary keyword naturally
- Body: Primary keyword in first 100 words; secondary keywords in H2–H6 and body
- Logical H2–H6 structure for scannability and LLM/AI Overview visibility
Schema: Add Organization + WebSite JSON-LD on homepage (or in root layout for site-wide). Organization establishes brand entity; WebSite enables sitelinks searchbox. Do not put Organization only on About page—About uses AboutPage schema. See schema-markup, entity-seo.
Output Format
- Structure outline (sections)
- Hero copy options (headline, subheadline, CTA)
- Key sections content suggestions
- SEO metadata (title, description, H1)
- Conversion checklist
Related Skills
- branding: Brand strategy, value prop, differentiation; homepage implements brand voice
- brand-protection: "Official website" placement when impersonation risk exists
- landing-page-generator: For single-goal campaign pages (affiliate signup, lead capture); homepage is multi-purpose
- pricing-page-generator: Homepage often links to pricing
- features-page-generator: Features section or link to features page
- press-coverage-page-generator: "As Seen In" section (logo strip) when coverage exists; full page links from homepage
- customer-stories-page-generator: Testimonials, case study snippets for social proof section
- schema-markup, entity-seo: Organization + WebSite schema placement (homepage or root layout)
- title-tag, meta-description, page-metadata, open-graph, twitter-cards: Homepage metadata and social previews
- heading-structure: Homepage heading structure
How to use homepage-generator on Cursor
AI-first code editor with Composer
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 homepage-generator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches homepage-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate homepage-generator. Access the skill through slash commands (e.g., /homepage-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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★65 reviews- ★★★★★Amelia Mehta· Dec 28, 2024
homepage-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Dec 16, 2024
homepage-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mateo Reddy· Dec 16, 2024
homepage-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Rahul Santra· Dec 12, 2024
homepage-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ishan Ghosh· Dec 8, 2024
Useful defaults in homepage-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amelia Huang· Dec 8, 2024
homepage-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Diya Dixit· Dec 4, 2024
I recommend homepage-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mateo Sethi· Nov 27, 2024
We added homepage-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amelia Rahman· Nov 27, 2024
Solid pick for teams standardizing on skills: homepage-generator is focused, and the summary matches what you get after install.
- ★★★★★Mateo Shah· Nov 23, 2024
Keeps context tight: homepage-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 65