jezweb/claude-skills

landing-page

Generate a complete, deployable landing page from a brief.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jezweb/claude-skills --skill landing-page

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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:

FieldRequiredExample
Business/product nameYes"Acme Plumbing"
Value propositionYes"24/7 emergency plumbing across Newcastle"
Target audienceYes"Homeowners in the Hunter Valley"
Primary CTAYes"Call Now" / "Get a Quote" / "Sign Up"
Secondary CTANo"Learn More" / "View Pricing"
Brand coloursNoPrimary: #1E40AF, accent: #F59E0B
Logo URL or textNoURL to logo image, or just use business name
Phone / emailNoFor contact section
Sections wantedNoDefault: 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:

html
<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

RequestApproach
"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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
jezweb
커뮤니티

app-docs

Generate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate use

1시간 설치 수
2
GitHub Stars
1.1천
업데이트
10월 9일
jezweb
커뮤니티

deep-research

Deep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6 hours). Triggers: 'research this', 'discovery', 'explore the space', 'what should I build', 'competitive analysis', 'before I start building', 'research before coding'. Not for cited

1시간 설치 수
1
GitHub Stars
1.1천
업데이트
10월 9일
jezweb
커뮤니티

wordpress-elementor

Edit Elementor pages and manage templates on WordPress sites via browser automation (for visual / structural changes) or WP-CLI (for safe text replacements). Use whenever the user wants to edit an Elementor page, update text in Elementor widgets, apply or manage Elementor templates, or make content changes to pages built with the Elementor page builder.

1시간 설치 수
2
GitHub Stars
1.1천
업데이트
10월 9일
jezweb
커뮤니티

image-processing

Process images for web development — resize, crop, trim whitespace, convert formats (PNG/WebP/JPG), optimise file size, generate thumbnails, create OG card images. Uses Pillow (Python) — no ImageMagick needed. Trigger with 'resize image', 'convert to webp', 'trim logo', 'optimise images', 'make thumbnail', 'create OG image', 'crop whitespace', 'process image', or 'image too large'.

1시간 설치 수
1
GitHub Stars
1.1천
업데이트
10월 9일