跳到正文
cccskills
免费在 GitHub 公开

landing-page-generator

Turn repository documentation and images into a complete landing page with features, setup instructions, and FAQs. Generate static HTML, CSS, and JavaScript files, plus a GitHub Actions workflow for publishing on GitHub Pages.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.

查看安装方法

适用场景

  • Turning a README into a project showcase page
  • Creating a homepage for an open-source project
  • Standardizing landing pages across projects
  • Adding screenshots and pricing to a project page

包含的文件(13)

  • SKILL.md7.3 KB
  • assets/search-base.js10.8 KB
  • assets/section-snippets/faq.html1.6 KB
  • assets/section-snippets/features-grid.html1.9 KB
  • assets/section-snippets/footer.html1.1 KB
  • assets/section-snippets/header.html1.8 KB
  • assets/section-snippets/hero.html1.4 KB
  • assets/section-snippets/install.html2.2 KB
  • assets/section-snippets/risk-banner.html629 B
  • assets/section-snippets/search-modal.html1.4 KB
  • assets/static-workflow.yml1.2 KB
  • assets/styles-base.css17.9 KB
  • references/landing-pattern.md11.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Landing page generator

Generate a complete, deploy-ready landing page from any repository by analyzing its documentation and structure.

When to use this skill

  • Creating a landing page for a GitHub repository
  • Generating static sites from existing documentation
  • Standardizing landing pages across multiple projects
  • Converting README content to marketing/showcase pages

What this skill does

  1. Analyze Repository: Read README.md, CHANGELOG.md, package.json/VERSION, docs/, assets/
  2. Extract Content: Identify title, tagline, features, installation, screenshots
  3. Map to Sections: Hero, Features, Install, FAQ, Footer (+ optional: Risk Banner, Pricing)
  4. Generate Landing: Create complete static site (HTML + CSS + JS)
  5. Deploy-Ready Output: Include GitHub Actions workflow for GitHub Pages

How to use

Basic usage

/landing-page-generator from ~/path/to/repo

With options

/landing-page-generator from ~/path/to/repo --risk-banner --pricing-table

Available options

OptionDescriptionDefault
--risk-bannerAdd prominent warning/disclaimer banner above foldfalse
--pricing-tableInclude pricing comparison sectionfalse
--screenshots <path>Path to screenshots folder./assets/
--theme [dark|light]Color theme variantdark
--searchEnable Cmd+K searchtrue
--output <path>Output directory./[repo-name]-landing/

Workflow

Step 1: Repository analysis

Read and analyze these files from the source repo:

README.md        → Primary content source (title, tagline, features, install)
CHANGELOG.md     → Version info, recent changes
package.json     → Version number, dependencies, metadata
VERSION          → Alternative version source
docs/            → Additional documentation pages
assets/          → Screenshots, images
LICENSE          → License type for badge

Step 2: Content extraction map

SourceTarget SectionExtraction Method
README title/badgesHeroFirst H1 + shield.io badge lines
README TL;DRHero taglineFirst paragraph or blockquote after title
README featuresFeatures gridH2/H3 sections with bullet lists
README installQuick StartCode blocks with shell commands
README usageExamplesCode blocks with examples
README FAQFAQDetails/summary or H3+P patterns
CHANGELOGWhat's NewLatest 1-3 releases
assets/*.pngScreenshotsGallery section

Step 3: Section generation

Generate these sections in order:

  1. Header (sticky)

    • Logo/project name
    • Nav links: Features, Install, FAQ
    • Actions: Search (Cmd+K), GitHub Star, primary CTA
  2. Risk Banner (if --risk-banner)

    • Orange/warning style above fold
    • Clear, visible disclaimer text
    • Link to detailed disclosure section
  3. Hero Section

    • Title from README H1
    • Tagline from TL;DR/first paragraph
    • Stats badges (version, license, platform)
    • CTAs: "Quick Start" (primary), "View on GitHub" (secondary)
  4. Architecture/Overview (if diagram in README)

    • ASCII diagram converted to styled block
    • Or overview cards
  5. Features Grid

    • 4-6 feature cards from README features
    • Icon + title + description pattern
  6. Pricing Table (if --pricing-table)

    • Plans comparison table
    • Multipliers/usage table if present
  7. Screenshots Gallery (if assets exist)

    • Tab-based or carousel gallery
    • Captions from alt text
  8. Quick Start Section

    • One-liner install command (featured code block)
    • Setup steps
    • First usage example
  9. Risk Disclosure (if --risk-banner)

    • Full disclaimer section
    • ToS considerations
    • Recommendations
  10. FAQ Section

    • Generated from README FAQ or common questions
    • Collapsible details pattern
  11. Related Projects (if links in README)

    • Cards linking to dependencies/related repos
  12. Footer

    • Quick links
    • License badge
    • Version info
    • Author/repo links

Step 4: Output structure

[project-name]-landing/
├── index.html              # Main landing page
├── styles.css              # Complete stylesheet
├── search.js               # Cmd+K search functionality
├── search-data.js          # Search index (FAQ, features)
├── favicon.svg             # Generated or copied
├── robots.txt              # SEO
├── CLAUDE.md               # Project instructions
├── README.md               # Landing repo documentation
├── assets/                 # Copied screenshots
│   └── [copied from source]
└── .github/
    └── workflows/
        └── static.yml      # GitHub Pages deployment

Step 5: Validation checkpoint

Before finalizing, verify:

  • All sections render correctly in a browser
  • Links point to valid targets (GitHub repo, docs, install commands)
  • Responsive layout works at mobile (375px), tablet (768px), and desktop (1280px) widths
  • Accessibility: skip links present, ARIA labels on interactive elements, color contrast passes WCAG AA

Tech stack

  • No build step: Pure HTML + CSS + JS
  • Search: MiniSearch lazy-loaded from CDN with fallback
  • Deployment: GitHub Pages via Actions
  • Styling: CSS custom properties, responsive, dark theme default
  • Accessibility: Skip links, ARIA labels, keyboard navigation

CSS Patterns (from established landings)

Component classes

/* Buttons */
.btn, .btn-primary, .btn-secondary, .btn-github-star, .btn-outline

/* Cards */
.feature-card, .comparison-card, .path-card

/* Layout */
.container, .features-grid, .hero, .section

/* Utilities */
.visually-hidden, .skip-link

CSS variables

:root {
  --color-bg: #0d1117;
  --color-surface: #161b22;
  --color-border: #30363d;
  --color-text: #c9d1d9;
  --color-text-muted: #8b949e;
  --color-primary: #58a6ff;
  --color-success: #3fb950;
  --color-warning: #d29922;
  --color-danger: #f85149;
  --space-xs: 0.25rem;
  --space-sm: 0.5rem;
  --space-md: 1rem;
  --space-lg: 1.5rem;
  --space-xl: 2rem;
  --radius: 6px;
}

Example

User: /landing-page-generator from ~/projects/my-project --risk-banner --pricing-table

Output:

Creates ~/projects/my-project-landing/ with:

  • Complete landing page showcasing the multi-provider router
  • Prominent ToS risk banner (orange, above fold)
  • Provider cards (Anthropic, Copilot, Ollama)
  • Pricing tables from README
  • Screenshots gallery
  • GitHub Pages deployment ready

Tips

  • Always include --risk-banner for projects with legal/ToS considerations
  • Screenshots significantly improve landing quality - ensure assets/ is populated
  • The skill preserves README language (English/French)
  • Review generated FAQ - may need customization
  • Test responsive design after generation

References

See references/landing-pattern.md for detailed pattern documentation. See assets/ for reusable templates and snippets.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

中文简介正在准备中。当前显示英语简介。

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

中文简介正在准备中。当前显示英语简介。

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

中文简介正在准备中。当前显示英语简介。

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

best-of-n

免费

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

中文简介正在准备中。当前显示英语简介。

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

canary

免费

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

中文简介正在准备中。当前显示英语简介。

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

catchup

免费

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

中文简介正在准备中。当前显示英语简介。

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide62062026年10月20日 更新

查看 FlorianBruniaux 的全部技能

报告此技能的问题