Communitygithub.com

xzedm/clipplic-landing

将应用和网站部署到 Vercel。当用户请求部署操作时使用,例如“部署我的应用”、“部署并给我链接”、“推送上线”或“创建预览部署”。

clipplic-landing 是什么?

该技能用于将项目部署到 Vercel 平台,帮助开发者快速完成从本地项目到线上环境的部署流程。它支持多种部署方式,包括通过 Git 推送、Vercel CLI 直接部署,以及免认证的回退脚本。技能会自动检测项目状态(是否已关联 Vercel、是否存在 Git 远程仓库、CLI 是否已认证),然后选择最优的部署路径。 技能覆盖多种使用场景:在终端环境(如 Claude Code)中可直接使用 CLI 命令;在沙箱环境(如 claude.ai 或 Codex)中优先尝试 CLI,失败后自动使用免认证部署脚本。无论哪种方式,都会最终返回预览 URL(和可选的认领 URL),让用户立即访问或转交到自己的 Vercel 账户。 此外,技能还处理团队选择、生产/预览部署区分、以及故障排查(如网络限制、认证失败时的回退策略),确保用户在不同环境下都能顺利完成部署。

兼容平台✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/xzedm/clipplic-landing/tree/HEAD/.agents/skills/deploy-to-vercel

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

部署到 Vercel

将任何项目部署到 Vercel。始终以预览(preview)方式部署,除非用户明确要求生产环境(production)。

目标是让用户进入最佳长期工作流程:项目通过 Git 推送与 Vercel 关联,实现自动部署。以下每种方法都尝试让用户更接近这种状态。

步骤 1:收集项目状态

在决定使用哪种方法之前,先运行以下四个检查:

# 1. 检查 Git 远程仓库
出 git remote get-url origin 2>/dev/null

# 2. 检查是否本地关联了 Vercel 项目(任一文件存在都表示已关联)
出 cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null

# 3. 检查 Vercel CLI 是否已安装并已认证
出 vercel whoami 2>/dev/null

# 4. 列出可用团队(如果已认证)
出 vercel teams list --format json 2>/dev/null

团队选择

如果用户属于多个团队,以项目符号列表呈现所有可用的团队 slug,并询问要部署到哪个团队。用户选择团队后,立即进入下一步,无需额外确认。

在所有后续 CLI 命令(vercel deploy、vercel link、vercel inspect 等)中通过 --scope 传入团队 slug:

vercel deploy [path] -y --no-wait --scope <team-slug>

如果项目已关联(存在 .vercel/project.json 或 .vercel/repo.json),这些文件中的 orgId 决定了团队,无需再次询问。如果只有一个团队(或仅个人账户),跳过提示,直接使用。

关于 .vercel/ 目录: 已关联的项目具有以下两种文件之一:

  • .vercel/project.json:由 vercel link 创建(单项目关联)。包含 projectId 和 orgId。
  • .vercel/repo.json:由 vercel link --repo 创建(基于仓库的关联)。包含 orgId、remoteName 以及一个将目录映射到 Vercel 项目 ID 的 projects 数组。

任一文件存在都表示项目已关联。请同时检查两者。

不要在未关联的目录中使用 vercel project inspect、vercel ls 或 vercel link 来检测状态;没有 .vercel/ 配置时,它们会交互式提示(或者使用 --yes 时静默关联,产生副作用)。只有 vercel whoami 在任何目录下都是安全的。

步骤 2:选择部署方法

已关联(存在 .vercel/)+ 有 Git 远程仓库 → Git 推送

这是理想状态。项目已关联并具有 Git 集成。

  1. 在推送前先询问用户。 未经明确批准绝不推送:

    此项目已通过 Git 连接到 Vercel。我可以提交并推送以触发部署。是否继续?
    
  2. 提交并推送:

    git add .
    git commit -m "deploy: <更改描述>"
    git push
    

    Vercel 会从推送自动构建。非生产分支获得预览部署;生产分支(通常是 main)获得生产部署。

  3. 获取预览 URL。 如果 CLI 已认证:

    sleep 5
    vercel ls --format json
    

    JSON 输出包含一个 deployments 数组。找到最新条目。其 url 字段即为预览 URL。

    如果 CLI 未认证,告诉用户查看 Vercel 仪表盘或 Git 提供商的提交状态检查以获取预览 URL。


已关联(存在 .vercel/)+ 无 Git 远程仓库 → vercel deploy

项目已关联但没有 Git 仓库。直接使用 CLI 部署。

vercel deploy [path] -y --no-wait

使用 --no-wait 让 CLI 立即返回部署 URL,而不是阻塞到构建完成(构建可能需要一段时间)。然后使用以下命令检查部署状态:

vercel inspect <deployment-url>

对于生产部署(仅当用户明确要求时):

vercel deploy [path] --prod -y --no-wait

未关联 + CLI 已认证 → 先关联,再部署

CLI 可用,但项目尚未关联。这是让用户进入最佳状态的机会。

  1. 询问用户要部署到哪个团队。 以项目符号列表呈现步骤 1 中的团队 slug。如果只有一个团队(或仅个人账户),跳过此步骤。

  2. 一旦选择了团队,直接进行关联。 告知用户接下来会发生什么,但不要要求单独确认:

    正在将此项目关联到 <team name> 上的 Vercel。这将创建一个 Vercel 项目用于部署,并启用未来 Git 推送的自动部署。
    
  3. 如果存在 Git 远程仓库,使用基于仓库的关联,指定所选团队范围:

    vercel link --repo --scope <team-slug>
    

    这会读取 Git 远程 URL 并将其匹配到从该仓库部署的现有 Vercel 项目。它会创建 .vercel/repo.json。这比 vercel link(不带 --repo)可靠得多,后者尝试按目录名称匹配,当本地文件夹与 Vercel 项目名称不同时常常失败。

    如果没有 Git 远程仓库,回退到标准关联:

    vercel link --scope <team-slug>
    

    这会提示用户选择或创建项目。它会创建 .vercel/project.json。

  4. 然后使用最佳可用方法部署:

    • 如果存在 Git 远程仓库 → 提交并推送(参见上面的 Git 推送方法)
    • 如果没有 Git 远程仓库 → vercel deploy [path] -y --no-wait --scope <team-slug>,然后使用 vercel inspect <url> 检查状态

未关联 + CLI 未认证 → 安装、认证、关联、部署

Vercel CLI 尚未安装。

  1. 安装 CLI(如果尚未安装):

    npm install -g vercel
    
  2. 认证:

    vercel login
    

    用户在浏览器中完成认证。如果在非交互式环境中无法登录,请跳转到下面的免认证回退。

  3. 询问要部署到哪个团队:以项目符号列表呈现 vercel teams list --format json 中的团队 slug。如果只有一个团队/个人账户,跳过。一旦选择,立即继续。

  4. 使用所选团队范围关联项目(如果存在 Git 远程仓库则使用 --repo,否则使用普通 vercel link):

    vercel link --repo --scope <team-slug>   # 如果存在 Git 远程仓库
    vercel link --scope <team-slug>          # 如果没有 Git 远程仓库
    
  5. 使用最佳可用方法部署(如果存在远程仓库则 Git 推送,否则 vercel deploy -y --no-wait --scope <team-slug>,然后使用 vercel inspect <url> 检查状态)。


免认证回退,claude.ai 沙箱

何时使用: 当 CLI 无法在 claude.ai 沙箱中安装或认证时的最后手段。这不需要认证。它返回一个预览 URL(在线站点)和一个认领 URL(转移到你的 Vercel 账户)。

bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh [path]

参数:

  • path - 要部署的目录,或一个 .tgz 文件(默认为当前目录)

示例:

# 部署当前目录
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh

# 部署特定项目
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh /path/to/project

# 部署已有的 tarball
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh /path/to/project.tgz

脚本会从 package.json 自动检测框架,打包项目(排除 node_modules、.git、.env),上传并等待构建完成。

告诉用户: “您的部署已就绪,访问 [previewUrl]。在 [claimUrl] 处认领以管理您的部署。”


免认证回退,Codex 沙箱

何时使用: 在 Codex 沙箱中,CLI 可能未认证。Codex 默认在沙箱环境中运行,先尝试 CLI,如果认证失败则回退到部署脚本。

  1. 检查 Vercel CLI 是否已安装(此检查无需提升权限):

    command -v vercel
    
  2. 如果安装了 vercel,尝试使用 CLI 部署:

    vercel deploy [path] -y --no-wait
    
  3. 如果未安装 vercel,或 CLI 失败并显示“No existing credentials found”,使用回退脚本:

    skill_dir="<skill-安装路径>"
    
    # 部署当前目录
    bash "$skill_dir/resources/deploy-codex.sh"
    
    # 部署特定项目
    bash "$skill_dir/resources/deploy-codex.sh" /path/to/project
    
    # 部署已有 tarball
    bash "$skill_dir/resources/deploy-codex.sh" /path/to/project.tgz
    

脚本处理框架检测、打包和部署。它等待构建完成并返回包含 previewUrl 和 claimUrl 的 JSON。

告诉用户: “您的部署已就绪,访问 [previewUrl]。在 [claimUrl] 处认领以管理您的部署。”

提升网络访问权限: 仅当沙箱阻止网络调用时(sandbox_permissions=require_escalated)才提升实际部署命令的权限。不要提升 command -v vercel 检查的权限。


特定于代理的说明

Claude Code / 基于终端的代理

您拥有完整的 shell 访问权限。不要使用 /mnt/skills/ 路径。按照上述决策流程直接使用 CLI。

对于免认证回退,从技能安装位置运行部署脚本:

bash ~/.claude/skills/deploy-to-vercel/resources/deploy.sh [path]

路径可能因用户安装技能的位置而异。

沙箱环境(claude.ai)

您很可能无法运行 vercel login 或 git push。直接转到免认证回退,claude.ai 沙箱。

Codex

Codex 在沙箱中运行。首先检查 CLI 是否可用,然后回退到部署脚本。转到免认证回退,Codex 沙箱。


输出

始终向用户显示部署 URL。

  • Git 推送: 使用 vercel ls --format json 查找预览 URL。如果 CLI 未认证,告诉用户查看 Vercel 仪表盘或提交状态检查。
  • CLI 部署: 显示 vercel deploy --no-wait 返回的 URL。使用 vercel inspect <url> 检查构建状态并报告给用户。
  • 免认证回退: 同时显示预览 URL 和认领 URL:
    部署成功!
    
    预览 URL: https://my-app-abc123.vercel.app
    认领 URL: https://vercel.com/claim-deployment?code=...
    
    请通过预览 URL 查看您的站点。
    要将此部署转移到您的 Vercel 账户,请访问认领 URL。
    

不要通过 curl 或 fetch 访问已部署的 URL 来验证其是否正常工作。只需返回链接。


故障排查

网络出口错误(claude.ai)

如果由于 claude.ai 上的网络限制导致部署失败,请告诉用户:

由于网络限制,部署失败。要解决此问题:

1. 前往 https://claude.ai/settings/capabilities
2. 将 *.vercel.com 添加到允许的域名
3. 再次尝试部署

提升网络访问权限(Codex / 沙箱环境)

如果在沙箱环境中由于网络问题(超时、DNS 错误、连接重置)导致部署失败,请使用提升的权限重新运行(sandbox_permissions=require_escalated)。不要提升初始 CLI 可用性检查的权限,仅提升实际部署命令的权限。

给用户的示例引导:

部署需要提升网络访问权限才能部署到 Vercel。我可以重新运行该命令并提升权限,是否继续?

CLI 认证失败

如果 vercel login 或 vercel deploy 因认证错误失败,回退到免认证部署脚本(根据环境选择 claude.ai 或 Codex 版本)。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

xzedm/clipplic-landing

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

xzedm/clipplic-landing

Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance.

xzedm/clipplic-landing

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

xzedm/clipplic-landing

Design iOS apps following Apple's Human Interface Guidelines. Generate native components, validate designs, and ensure accessibility compliance for iPhone, iPad, and Apple Watch.

xzedm/clipplic-landing

Redesign mobile app UI to feel unmistakably Apple-like, iOS-forward, and native. Use this skill when building iOS apps, applying Apple Human Interface Guidelines, or creating native-feeling mobile interfaces with SF Pro typography, translucency, and system-like components.

xzedm/clipplic-landing

Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says "make this accessible" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, "not keyboard accessible".

xzedm/clipplic-landing

OKLCH color space and color usage for web projects. Convert hex/rgb/hsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.

xzedm/clipplic-landing

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

xzedm/clipplic-landing

Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or reviewing frontend code for typography. Triggers on typography, fonts, font formats, woff2, variable fonts, font-weight, opentype, font-feature-settings, letter-spacing, line-height, type scale, heading hierarchy, heading levels, tabular numbers, text-wrap, truncation, line clamp, underlines, text-decoration, text selection, iOS input zoom, scaled input text, font smoothing, text contrast, measure, line length, text-box, smart punctuation, drop cap.

xzedm/clipplic-landing

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter/exit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.

xzedm/clipplic-landing

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

xzedm/clipplic-landing

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

xzedm/clipplic-landing

Extract design primitives from a public website and generate starter token files for your project.

xzedm/clipplic-landing

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.

xzedm/clipplic-landing

**MANDATORY prerequisite**: you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context, e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

xzedm/clipplic-landing

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

xzedm/clipplic-landing

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications.

xzedm/clipplic-landing

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

xzedm/clipplic-landing

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

xzedm/clipplic-landing

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic. A promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

相关技能