explainx.ainewsletter3.4k
Productivity

landing-page▌

jezweb/claude-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/jezweb/claude-skills --skill landing-page
0 commentsdiscussion
summary

Generate a complete, deployable landing page as a single HTML file. No build step, no dependencies — open it in a browser or deploy anywhere.

skill.md

Landing Page Generator

Generate a complete, deployable landing page as a single HTML file. No build step, no dependencies — open it in a browser or deploy anywhere.

Workflow

1. Gather the Brief

Ask the user for:

Field Required Example
Business/product name Yes "Acme Plumbing"
Value proposition Yes "24/7 emergency plumbing across Newcastle"
Target audience Yes "Homeowners in the Hunter Valley"
Primary CTA Yes "Call Now" / "Get a Quote" / "Sign Up"
Secondary CTA No "Learn More" / "View Pricing"
Brand colours No Primary: #1E40AF, accent: #F59E0B
Logo URL or text No URL to logo image, or just use business name
Phone / email No For contact section
Sections wanted No Default: hero, features, testimonials, FAQ, footer

If no brand colours provided, suggest using the color-palette skill to generate them, or use a sensible default (slate/blue).

2. Generate the HTML

Produce a single HTML file with:

<!DOCTYPE html>
<html lang="en" class="scroll-smooth">
<head>
  <!-- Meta, OG tags, favicon -->
  <script src="https://cdn.tailwindcss.com"></script>
  <script>tailwind config with custom colours</script>
</head>
<body>
  <!-- Nav -->
  <!-- Hero -->
  <!-- Features -->
  <!-- Social Proof -->
  <!-- Pricing (optional) -->
  <!-- FAQ -->
  <!-- Footer -->
  <!-- Dark mode toggle script -->
</body>
</html>

3. Section Patterns

Navigation

  • Sticky top nav with logo/name + anchor links to sections
  • Mobile hamburger menu (CSS-only or minimal JS)
  • CTA button in nav (right-aligned)

Hero

  • Full-width, above the fold
  • Headline (h1) — the value proposition, not the business name
  • Subheadline — supporting detail, 1-2 sentences
  • Primary CTA button (large, contrasting colour)
  • Optional: hero image placeholder or gradient background
  • Pattern: text-left on desktop (60/40 split with image), centred on mobile

Features / Services

  • 3-6 items in a responsive grid (1 col mobile, 2-3 cols desktop)
  • Each: icon placeholder + heading + short description
  • Use semantic headings (h2 for section, h3 for items)

Social Proof / Testimonials

  • 2-3 testimonial cards with quote, name, role/company
  • Star rating if applicable
  • Alternative: logo bar of client/partner logos

Pricing (optional)

  • 2-3 tier cards (basic/pro/enterprise pattern)
  • Highlighted "recommended" tier
  • Feature comparison list per tier
  • CTA button per tier

FAQ

  • Accordion pattern (details/summary — no JS needed)
  • 4-6 common questions
  • Schema.org FAQPage markup for SEO

Footer

  • Business name, contact info, social links
  • Legal links (privacy, terms) as placeholders
  • Copyright year (use JS for auto-update)

4. Technical Requirements

Responsive: Mobile-first with three breakpoints

Default: mobile (< 640px)
sm: 640px+ (tablet)
lg: 1024px+ (desktop)

Dark mode: Three-state toggle (light/dark/system)

  • CSS custom properties for colours
  • .dark class on <html> — no CSS media query
  • Small JS snippet for toggle + localStorage persistence

Accessibility:

  • Proper heading hierarchy (h1 → h2 → h3, no skips)
  • Alt text placeholders on all images
  • Focus-visible styles on interactive elements
  • Sufficient colour contrast (4.5:1 minimum)
  • Skip-to-content link

SEO:

  • Semantic HTML5 elements (header, main, section, footer)
  • OG meta tags (title, description, image, url)
  • Twitter card meta tags
  • Canonical URL
  • JSON-LD for LocalBusiness if it's a local business (reference seo-local-business skill)

Performance:

  • No JS required for core content rendering
  • Lazy-load images (loading="lazy")
  • System font stack (no external font requests)
  • Single file — no external CSS/JS beyond Tailwind CDN

5. Colour Application

If user provides brand colours, configure Tailwind inline:

<script>
tailwind.config = {
  darkMode: 'class',
  theme: {
    extend: {
      colors: {
        primary: { DEFAULT: '#1E40AF', light: '#3B82F6', dark: '#1E3A8A' },
        accent: { DEFAULT: '#F59E0B', light: '#FBBF24', dark: '#D97706' },
      }
    }
  }
}
</script>

If no colours provided, use Tailwind's built-in palette (slate for neutrals, blue for primary).

6. Output

Write the file to the user's specified location, or default to ./index.html.

After generating:

  1. Tell the user how to preview: open index.html (macOS) or python3 -m http.server for a local server
  2. Suggest deployment options: drag to Cloudflare Pages, Netlify drop, or wrangler deploy for Workers
  3. List placeholder content that needs replacing (images, testimonials, phone numbers)

Quality Rules

  1. No placeholder lorem ipsum — generate realistic placeholder text based on the business type
  2. No broken layouts — test the responsive grid mentally: 1 col → 2 col → 3 col
  3. No inline styles — use Tailwind classes exclusively
  4. Real interactions — smooth scroll to sections, working accordion, working dark mode toggle
  5. Accessible by default — don't sacrifice accessibility for aesthetics
  6. Australian conventions — if the business is Australian, use +61 phone format, Australian spelling, ABN placeholder

Variations

Request Approach
"Coming soon page" Hero only + email signup form + countdown timer
"Product launch" Hero + features + pricing + CTA-heavy
"Portfolio" Hero + project grid + about + contact
"Event page" Hero + schedule + speakers + venue + register CTA
"App download" Hero + features + screenshots + app store badges

Adapt the section selection to match the page purpose. Not every page needs pricing or FAQ.

how to use landing-page

How to use landing-page 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 landing-page
2

Execute installation command

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

$npx skills add https://github.com/jezweb/claude-skills --skill landing-page

The skills CLI fetches landing-page from GitHub repository jezweb/claude-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/landing-page

Reload or restart Cursor to activate landing-page. Access the skill through slash commands (e.g., /landing-page) 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.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

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.7★★★★★45 reviews
  • ★★★★★Liam Mehta· Dec 28, 2024

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

  • ★★★★★Chaitanya Patil· Dec 24, 2024

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

  • ★★★★★Aarav Kim· Dec 16, 2024

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

  • ★★★★★Henry Iyer· Dec 8, 2024

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

  • ★★★★★Evelyn Martinez· Dec 4, 2024

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

  • ★★★★★Aarav Abbas· Nov 23, 2024

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

  • ★★★★★Aarav Okafor· Nov 19, 2024

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

  • ★★★★★Piyush G· Nov 15, 2024

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

  • ★★★★★Ama Li· Nov 7, 2024

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

  • ★★★★★Emma Gupta· Oct 26, 2024

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

showing 1-10 of 45

1 / 5