Token导航 LogoToken导航

Agent Skill · 前端设计

frontend-landings(前端登陆)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

frontend-landings 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有未通过项,按安装量在前端设计类的 10,216 个 Skill 里排第 5,261。

总安装 706周安装 30GitHub Stars 1下载 247核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:frontend-landings(前端登陆)
来源仓库:https://github.com/auwalmusa/frontend-landings-claude-skill
仓库路径:skills/frontend-landings
安装命令:
npx skills add https://github.com/auwalmusa/frontend-landings-claude-skill --skill frontend-landings
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/auwalmusa/frontend-landings-claude-skill --skill frontend-landings

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

生成营销落地页与展示型页面的响应式代码。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。支持 Hero Section、CTA 区块等常见组件模板。适配 Tailwind CSS 与移动端优先设计原则。建议预览不同断点效果,确保跨设备一致性。

frontend-landings 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/frontend-landings

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/auwalmusa/frontend-landings-claude-skill --ski…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

frontend-landings 怎么安装?

在终端执行 npx skills add https://github.com/auwalmusa/frontend-landings-claude-skill --skill fronten…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

frontend-landings 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

frontend-landings 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

frontend-landings 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

frontend-landings 用的人多吗?

公开数据是累计安装 706 次,近一周安装 30 次,下载 247 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

frontend-landings 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
frontend-landings

前端登陆 · 本页

7061需要联网未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Frontend Landings

Generate stunning, zero-build, single-file HTML landing pages with curated style presets, smooth animations, responsive design, and dark/light mode — all in one self-contained file.

Before You Start

Read the style presets reference file to understand available aesthetics:

references/STYLE_PRESETS.md

Two Modes of Operation

Mode 1: From Scratch

User provides product details → generate a complete landing page.

Gather these inputs (ask if not provided):

  1. Product/brand name (required)
  2. Tagline / hero headline (required)
  3. 3–6 key features or benefits (required)
  4. Target audience (helpful)
  5. Primary CTA (e.g., "Start Free Trial", "Join Waitlist") — default: "Get Started"
  6. Color preferences (optional — preset will handle this)
  7. Style preset (show the preset menu if not specified)

Mode 2: Improve / Convert

User provides existing HTML, a description, a screenshot, or a URL → enhance with better design, animations, and responsiveness.

Workflow:

  1. Analyze the existing design (structure, colors, typography, layout)
  2. Identify improvements (animations, responsiveness, accessibility, visual hierarchy)
  3. Ask which style preset to apply (or preserve existing aesthetic)
  4. Regenerate as a single-file HTML with all enhancements

Style Preset System

ALWAYS offer the preset menu at the start of any landing page task unless the user has already chosen one or explicitly described a specific aesthetic.

Present presets like this:

Pick a visual style for your landing page (type number or name):

 1. ☁️  Clean SaaS Minimal     — Crisp whites, subtle shadows, system-native feel
 2. 🔮  Glassmorphic Modern     — Frosted glass panels, gradients, translucency
 3. 🏗️  Bold Brutalist          — Raw concrete textures, monospace type, stark contrast
 4. 🌆  Cyberpunk Neon          — Dark backgrounds, electric glow, scanline effects
 5. ✒️  Elegant Serif Premium   — Editorial luxury, serif headlines, gold accents
 6. 🎨  Playful Gradients       — Bouncy animations, mesh gradients, rounded everything
 7. 🌙  Dark Mode First         — Deep blacks, neon accents, OLED-optimized
 8. 📻  Vintage Retro           — Warm sepia tones, retro type, nostalgic textures
 9. 🌿  Organic Nature          — Earth tones, organic shapes, botanical illustrations
10. 🏢  Corporate Professional  — Navy/slate palette, structured grid, trust-building

Or describe your own custom aesthetic!

After the user picks, read references/STYLE_PRESETS.md for the detailed CSS variables, font stacks, animation styles, and design tokens for that preset.


Output Requirements

Single-File HTML Architecture

Every output MUST be one complete, self-contained HTML file. Structure:

<!DOCTYPE html>
<html lang="en" class="scroll-smooth">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <!-- SEO Meta Tags -->
  <title>{Product Name} — {Tagline}</title>
  <meta name="description" content="{Concise product description}">
  <meta property="og:title" content="{Product Name}">
  <meta property="og:description" content="{Description}">
  <meta property="og:type" content="website">
  <meta name="twitter:card" content="summary_large_image">

  <!-- Tailwind CSS CDN -->
  <script src="https://cdn.tailwindcss.com"></script>

  <!-- Anime.js for animations -->
  <script src="https://cdnjs.cloudflare.com/ajax/libs/animejs/3.2.2/anime.min.js"></script>

  <!-- Google Fonts (preset-specific) -->
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
  <link href="https://fonts.googleapis.com/css2?family={Preset+Fonts}&display=swap" rel="stylesheet">

  <!-- Tailwind Config + Custom Theme -->
  <script>
    tailwind.config = {
      darkMode: 'class',
      theme: {
        extend: {
          // Preset-specific extensions
          fontFamily: { /* from preset */ },
          colors: { /* from preset */ },
        }
      }
    }
  </script>

  <style>
    /* CSS Custom Properties from preset */
    :root { /* light theme vars */ }
    .dark { /* dark theme vars */ }

    /* Scroll-triggered animation base classes */
    .reveal { opacity: 0; transform: translateY(30px); transition: all 0.8s cubic-bezier(0.16, 1, 0.3, 1); }
    .reveal.active { opacity: 1; transform: translateY(0); }

    /* Preset-specific custom styles */
  </style>
</head>
<body>
  <!-- All content here -->

  <script>
    // Dark mode toggle
    // Scroll reveal observer
    // Anime.js entrance animations
    // Interactive components (FAQ accordion, pricing toggle, etc.)
  </script>
</body>
</html>

CDN Stack (no others allowed)

  • Tailwind CSS: https://cdn.tailwindcss.com (with inline config)
  • Anime.js: https://cdnjs.cloudflare.com/ajax/libs/animejs/3.2.2/anime.min.js
  • Google Fonts: Only preset-specific fonts
  • Icons: Inline SVG only (Heroicons-style). NEVER use icon font CDNs.

Mandatory Features in Every Output

  1. Responsive Design — Mobile-first. Test mental model at 375px, 768px, 1280px.
  2. Dark/Light Mode — prefers-color-scheme auto-detection + manual toggle button in nav.
  3. Scroll Animations — IntersectionObserver-based reveal animations on all sections.
  4. Smooth Scrolling — scroll-smooth on html + JS for nav anchors.
  5. Accessibility — Semantic HTML5, ARIA labels on interactive elements, focus-visible styles, skip-to-content link, sufficient color contrast.
  6. SEO Meta Tags — title, description, og:title, og:description, og:type, twitter:card.
  7. Performance — Lazy-load images, efficient CSS, minimal JS.

Section Generation

Based on user input, intelligently include these sections. Not all are required — match to the product context:

Always Include:

  1. Navigation — Sticky/fixed nav with logo, links, dark mode toggle, primary CTA button
  2. Hero — Large headline + sub-headline + CTA button(s) + visual element (gradient, abstract shape, or image placeholder)
  3. Features — 3–6 feature cards/grid with inline SVG icons
  4. Final CTA — Full-width call-to-action banner with headline + button
  5. Footer — Links, copyright, social icons (inline SVG)

Include When Relevant:

  • Social Proof / Logos — "Trusted by" logo bar (use placeholder boxes with company-style names)
  • Testimonials — 2–3 quote cards with avatar placeholders
  • Pricing — 3 tiers with monthly/annual toggle (JS-powered)
  • FAQ — Accordion with smooth open/close animations
  • How It Works — 3-step process with numbered steps
  • Stats / Metrics — Animated counters (e.g., "10k+ users", "99.9% uptime")

Animation Playbook

Use these animation patterns consistently:

Scroll Reveal (IntersectionObserver)

const observer = new IntersectionObserver((entries) => {
  entries.forEach(entry => {
    if (entry.isIntersecting) {
      entry.target.classList.add('active');
    }
  });
}, { threshold: 0.1, rootMargin: '0px 0px -50px 0px' });

document.querySelectorAll('.reveal').forEach(el => observer.observe(el));

Staggered Entrance (Anime.js)

anime({
  targets: '.feature-card',
  opacity: [0, 1],
  translateY: [40, 0],
  delay: anime.stagger(100, { start: 300 }),
  easing: 'easeOutCubic',
  duration: 800
});

Hero Text Animation

anime({
  targets: '.hero-title .word',
  opacity: [0, 1],
  translateY: [20, 0],
  delay: anime.stagger(80),
  easing: 'easeOutExpo',
  duration: 1200
});

Hover Micro-interactions

Use CSS transitions for hovers — Anime.js only for complex sequences:

.card { transition: transform 0.3s cubic-bezier(0.16, 1, 0.3, 1), box-shadow 0.3s ease; }
.card:hover { transform: translateY(-4px); box-shadow: 0 20px 40px -12px rgba(0,0,0,0.15); }

Counter Animation

function animateCounter(el) {
  const target = parseInt(el.dataset.target);
  anime({
    targets: el,
    innerHTML: [0, target],
    round: 1,
    easing: 'easeInOutExpo',
    duration: 2000
  });
}

Dark Mode Implementation

// Check system preference and saved preference
const prefersDark = window.matchMedia('(prefers-color-scheme: dark)').matches;
const saved = localStorage.getItem('theme');
if (saved === 'dark' || (!saved && prefersDark)) {
  document.documentElement.classList.add('dark');
}

// Toggle function (bind to button)
function toggleDark() {
  document.documentElement.classList.toggle('dark');
  localStorage.setItem('theme',
    document.documentElement.classList.contains('dark') ? 'dark' : 'light'
  );
}

Toggle button in nav:

<button onclick="toggleDark()" aria-label="Toggle dark mode" class="p-2 rounded-lg hover:bg-gray-100 dark:hover:bg-gray-800 transition-colors">
  <!-- Sun icon (shown in dark mode) -->
  <svg class="hidden dark:block w-5 h-5" ...>...</svg>
  <!-- Moon icon (shown in light mode) -->
  <svg class="block dark:hidden w-5 h-5" ...>...</svg>
</button>

Typography & Anti-Generic Rules

NEVER use these fonts: Inter, Roboto, Arial, Helvetica, Open Sans, system-ui defaults.

Each preset specifies its own distinctive font pairing. Always load from Google Fonts CDN.

NEVER use default Tailwind colors without customization. Every preset defines a custom palette via CSS variables AND tailwind.config extend.

NEVER output a page that looks like every other AI-generated landing page. Each preset has specific differentiators — honor them.


Inline SVG Icons

Use Heroicons-style inline SVGs. Here's the pattern:

<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="1.5" stroke="currentColor" class="w-6 h-6">
  <path stroke-linecap="round" stroke-linejoin="round" d="..." />
</svg>

Include 6–8 commonly needed icons directly in the HTML. Choose contextually relevant icons for the product's features.


FAQ Accordion Implementation

document.querySelectorAll('.faq-btn').forEach(btn => {
  btn.addEventListener('click', () => {
    const content = btn.nextElementSibling;
    const icon = btn.querySelector('.faq-icon');
    const isOpen = content.style.maxHeight && content.style.maxHeight !== '0px';

    // Close all others
    document.querySelectorAll('.faq-content').forEach(c => { c.style.maxHeight = '0px'; });
    document.querySelectorAll('.faq-icon').forEach(i => { i.style.transform = 'rotate(0deg)'; });

    if (!isOpen) {
      content.style.maxHeight = content.scrollHeight + 'px';
      icon.style.transform = 'rotate(45deg)';
    }
  });
});

Pricing Toggle Implementation

const toggle = document.getElementById('pricing-toggle');
const monthlyPrices = document.querySelectorAll('.price-monthly');
const annualPrices = document.querySelectorAll('.price-annual');

toggle.addEventListener('change', () => {
  const isAnnual = toggle.checked;
  monthlyPrices.forEach(el => el.classList.toggle('hidden', isAnnual));
  annualPrices.forEach(el => el.classList.toggle('hidden', !isAnnual));
});

Final Output Instructions

After generating the HTML, ALWAYS append this guidance:

✅ Your landing page is ready!

To use it:
1. Copy the entire code above into a file called `index.html`
2. Open it in any browser — it works standalone, no build step needed

To deploy for free:
• Vercel: vercel.com → New Project → drag & drop your index.html
• Netlify: app.netlify.com → drag & drop your index.html
• GitHub Pages: Push to a repo → Settings → Pages → Deploy from main

To customize further:
• Colors: Edit the CSS variables in :root { } and .dark { }
• Content: All text is directly in the HTML — find and replace
• Fonts: Swap the Google Fonts link and font-family values
• Animations: Adjust timing in the Anime.js calls and CSS transitions

Quality Checklist

Before delivering, mentally verify:

  • Single file, no external dependencies beyond CDN links
  • Responsive at 375px, 768px, 1280px
  • Dark mode works (toggle + system preference)
  • All animations fire on scroll
  • Navigation links scroll smoothly to sections
  • All interactive elements have hover/focus states
  • ARIA labels on buttons, toggles, and interactive elements
  • No default Tailwind look — preset aesthetic is distinct
  • Meta tags present for SEO and social sharing
  • Footer includes current year via JS: new Date().getFullYear()
  • CTA buttons are prominent and styled per preset
  • Icons are inline SVG, not external fonts
  • Page loads fast — no blocking resources

平台分布

Codex

36.6%
按下载量换算90

Claude

32.47%
按下载量换算80

Cursor

17.89%
按下载量换算44

Gemini CLI

10.33%
按下载量换算26

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills