所有 Skills

Guide to Sonner, the React toast library — install and wire up the Toaster, pick the right toast() call, promise and loading toasts, updating, dismissing and persisting toasts, styling, theming and icons, positioning and multiple toasters. Use when working with Sonner or troubleshooting it — toasts that don't appear, appear twice, lose their styles, ignore Tailwind classes, sit behind a modal, or don't follow dark mode.

emilkowalski

获取

release

29Ktesting-qa

管理当前项目的版本发布。支持校验变更日志（changelog）、自动安装 git hooks 以及发布新版本。当用户发送“/release”、“release 1.0.5”、“cut a release”或询问发布流程时触发。注意：本 Skill 不会被模型自动调用。

tobi

获取

writing-guidelines

29Kwriting-content

审查文档/散文是否符合写作指南。当被要求“审查我的文档”、“检查写作风格”、“审计散文”、“审查文档语气和语调”或“对照写作手册检查此页面”时使用。

vercel-labs

获取

opencli-sitemap-author

28Kbrowser-web

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener

获取

vercel-optimize

28Ksecurity

用于对已部署项目（尤其是 Next.js、SvelteKit、Nuxt 以及部分 Astro 应用）进行 Vercel 成本与性能优化。先收集 Vercel 指标、用量、项目配置和代码扫描结果；仅调查有指标支持的候选方案；基于已验证的文件和版本感知的 Vercel/框架文档生成排序后的建议。触发场景：Vercel 账单降低、慢或昂贵的路由、缓存优化机会、函数调用次数、构建分钟数、快速数据传输、Core Web Vitals、Bot Management、Fluid compute 或成本分解请求。

vercel-labs

获取

qmd

28Kresearch-knowledge

使用 QMD 搜索本地 Markdown 知识库、笔记、文档和 Wiki。当用户要求查找笔记、检索文档、查看 Wiki、从已索引的 Markdown 中回答问题或设置 QMD 访问时使用。

tobi

获取

vercel-cli-with-tokens

28Kdevops-cloud

使用基于令牌的身份验证在 Vercel 上部署和管理项目。当使用 Vercel CLI 通过访问令牌而非交互式登录时使用——例如“部署到 Vercel”、“设置 Vercel”、“向 Vercel 添加环境变量”。

vercel-labs

获取

deploy-to-vercel

28Kagent-workflows

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

vercel-labs

获取

repomix-explorer

28Kcode-generation

Analyze or explore a codebase (remote or local repository) by packing it with the Repomix CLI, then reading and searching the generated output. Use when the user wants a high-level understanding of an unfamiliar or large repo, not a targeted edit. Trigger for: - Structure/overview: "analyze this repo", "what's the structure", "explain this codebase", "what's in vercel/next.js" - Pattern discovery across many files: "find all auth code", "where are the API endpoints", "show me all React components" - Metrics: "how many files/tokens", "largest files", "TypeScript vs JavaScript ratio" - Remote repos: any github.com URL or "owner/repo" the user wants explored DO NOT trigger for: - Editing, refactoring, or writing code in the current project - Reading or searching a known file/path in the local project (use Read or grep directly) - Single-symbol lookups in the local project answerable with one grep - Git operations, running tests, builds, or installs