Netlify
CloudCommonly used with
Skills using Netlify (63)
canary
Post-deploy monitoring: watch production after a deploy and alert on regressions
estimate-temps-savings
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temp
cli-discover
Discover which CLI tools are installed, their versions, and authentication status
coolify-operator
Master Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or official CLI.
readme-refresh
Audit and update a project README, or bootstrap a new one. Detects tech stack, versions, and services.
deploy
Deploy application to target platform. Use when user explicitly says 'deploy', 'push to production', 'ship it'. Handles Vercel, Netlify, AWS, GCP, DigitalOcean, and VPS with pre-deploy verification and health checks. Enforces cost allocation tags + Managed-vs-Self-Host crossover decisions so deploy choices map to actual unit economics, not hand-waved 'we'll optimize later'.
nuxt
Use when working on Nuxt 4+ projects — server routes, routing, middleware, composables, h3 v1 helpers, nitropack v2. Updated for Nuxt 4.3+.
nuxthub
Use when building NuxtHub v0.10.6 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, multi-cloud deployment (Cloudflare, Vercel), and the new hub:db, hub:kv, hub:blob virtual module imports.
astro-deployment
Use when deploying an Astro 7 app to Cloudflare, Vercel, Netlify, or Node.js — adapter setup, ISR patterns, edge middleware.
astro-framework-expert
Expert guide for Astro 5+ framework — Content Collections, Islands Architecture, View Transitions, partial hydration, and MDX integration / Panduan ahli framework Astro 5+ — Content Collections, Islands Architecture, View Transitions, partial hydration, dan integrasi MDX.
wjs-looping-feedback
Use when the user wants to add an in-site feedback loop to a website repo — a floating "提个建议" button where allowlisted visitors submit suggestions that become a GitHub Issue, which GitHub Actions turns into an automatic code change via Claude Code, auto-merges and deploys, and records on a /_feedback dashboard with one-click revert. Triggers — "给网站加个反馈对话框", "提一句话就自动改网站", "装上反馈闭环", "feedback loop", "/wjs-looping-feedback".
deno-deploy
Use when deploying Deno apps to production, asking about Deno Deploy, or working with `deno deploy` CLI commands. Covers deployment workflows, environment variables, KV database access, custom domains, the --tunnel flag for local development, and the `deno deploy` command reference.
deploy-verify
Post-deploy smoke test combining all 5 tools (Sentry + Supabase + Firecrawl MCPs, plus the Langfuse and Playwright CLIs) into one workflow. Auto-detects deployment context, checks Sentry for new errors (with Seer AI root-cause on P0s), verifies Supabase migration health and logs, confirms Langfuse trace pipeline, runs Playwright smoke test on critical paths, and produces a ship-or-rollback verdict. Works with any project. Use when asked to: "verify deploy", "post-deploy check", "smoke test production", "check if deploy is healthy", "ship or rollback", "post-release check", "verify release", "deploy health check", or "run post-deploy".
ship
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
astro-knowledge-patch
Astro
review-analyzer-skill
AI驱动的电商评论深度分析工具，支持22维度智能标签、用户画像识别、VOC洞察和可视化看板生成。 当用户需要以下功能时触发： - 分析电商产品评论（Amazon/eBay/AliExpress等平台） - 从评论中提取用户画像、痛点和VOC（客户之声） - 生成产品洞察报告和机会点分析 - 创建专业的可视化分析看板 - 进行竞品分析和市场定位研究 触发关键词：电商评论分析、评论分析、竞品分析、用户洞察、VOC分析、产品优化、市场调研、评论数据挖掘 AI Agent 约束：必须通过 AskUserQuestion 收集分析数量、AI引擎选择、报告署名后再执行分析
deployment-engineer
Plan and verify safe deployment using project-approved commands, checks, and rollback procedures.
setup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.
deploy
Deploy to production and verify health. Reads ship state, merges PR if applicable, detects platform (Vercel/Fly/Netlify/Railway/Render/GHA), waits for CI, triggers deploy, runs health check, offers rollback on failure. Flags: --url, --skip-ci-wait, --skip-health, #<number>.
claude-jobs
Find job openings at tech companies. Use when user asks about jobs, careers, openings, positions, roles, or salaries - either at specific companies or general tech job queries.
skill-manager
Detect project tech stack and disable irrelevant skills to save context window space. Use when the user says "manage skills", "optimize skills", "disable irrelevant skills", "skill manager", or asks which skills are relevant for this project.
cache-bust-deploy-validation
After a production deploy of a CDN-fronted site, force cache-bust on every validation request and inspect Age/cache-status headers — the CDN can serve a stale 200 with old content for hours, hiding a broken deploy. Use whenever validating a freshly-deployed web app, debugging "deploy completed but the live site shows the old version", or building a post-deploy smoke test.
add-analytics
Add privacy-respecting visit counts to a live site. Free options only, and no tracking people across the web. Use when they ask "is anyone visiting my site", "add analytics", or want proof of traffic for a resume line.
custom-domain
Connect a domain of their own to the person's site. Covers registrar selection, current registration and renewal prices, DNS, redirects, and HTTPS. Use when they say "I want my own domain", "get rid of the .github.io part", or "connect mysite.com".
deploy-anywhere
Put an existing project online with a free host. GitHub Pages, Cloudflare Pages, or Netlify, verified live. Use when they have files but no URL, say "how do I put this online", or want a site off localhost.
deployment
Hosting, deployment, CI/CD, and going live. Activated when Claude works with deployment configs, Dockerfiles, Vercel/Netlify configs, or deployment-related commands.
seo-check
Pre-commit SEO audit. Reviews pending git changes for SEO regressions (noindex, robots.txt, canonicals, metadata, redirects, structured data, headings) and crawls the affected routes like Googlebot to verify what search engines will actually see. Use before committing changes that touch pages, layouts, metadata, robots, sitemaps, redirects, or middleware — or whenever the user asks whether a change is SEO-safe.
discover
Extracts semantic memory from project analysis. Scans codebase, docs, and configs to understand tech stack, constraints, and goals.
deploy-planner
Deployment and DevOps agent that generates Dockerfiles, CI/CD configs, and step-by-step deployment guides for free hosting platforms. Triggers on: deploy, launch, hosting, Docker, CI/CD, production, go live, ship it.
deploy
Deploy the project to a hosting platform. Detects deployment configuration, runs pre-deploy checks, and guides first-time setup.
meteor-deployment
Use when deploying a Meteor 3 application. Triggers on meteor build, meteor deploy, Galaxy Push to Deploy, Galaxy Mode, Repository Mode, DEPLOY_HOSTNAME, Docker, Kubernetes, settings.json, METEOR_SETTINGS, MONGO_URL, MONGO_OPLOG_URL, ROOT_URL, PORT, HTTP_FORWARDED_COUNT, NODE_OPTIONS, health checks, pre-deploy commands, hot code push, --architecture os.linux.x86_64, --server-only, or a deployed Node.js version mismatch. Use this skill when the user asks about shipping the app, asks about production config, or asks about containerizing. For Cordova Android/iOS artifacts, signing, and native HCP compatibility use meteor-native; this skill owns the backend deployment.
deployment-architecture
ShipIt deployment architecture: auto-deploy on push via platform Git integration, GitHub Deployments API for status tracking, deployment status in PR lifecycle card. Load when working on deployment features.
design-link-in-bio
Generate a minimal single-column standalone HTML page — mobile-first at 375px width — for use as a link-in-bio destination. Contains: name/wordmark, short tagline, list of links (each a styled <a> block), social footer. Self-contained, works offline, deployable as-is to GitHub Pages or Netlify. Reads ./design/<brand-slug>/DESIGN.md, tokens.css, and components.html. Triggers include "link in bio", "linktree replacement", "bio page", "/link-in-bio".
coolify-self-hosted-paas
Alternativa autoalojada a Vercel, Heroku y Render: despliega apps, bases y servicios en tu propio servidor con git-push, SSL automatico y sin costo por asiento. Apache 2.0.
nuxt
Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.
nuxthub
Use when building NuxtHub v0.10.6 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, multi-cloud deployment (Cloudflare, Vercel), and the new hub:db, hub:kv, hub:blob virtual module imports.
readme-style
Samuhlo's README style: Swiss Grid Brutalism — script-run H1, numbered // sections, honest _note: margins, stack table with real tech only. Load when generating or refreshing a project README.
trip-itinerary-page
Build a single-file HTML website that turns a multi-day trip plan into an interactive, shareable itinerary page — sticky day-by-day navigation that auto-scrolls to the active day, a live countdown to arrival/departure, a booking/prep checklist, and a quick-reference "essentials" panel (meeting points, emergency numbers, local tips). Use this skill whenever the user is planning a trip — for themselves, a visiting friend, family, or a group — and wants to organize it as something they or someone else can check on their phone throughout the trip. Trigger this even if the user just asks for "a page," "a site," or "something I can send them" for a trip that's already been discussed in the conversation — a multi-day itinerary is the signal, the word "itinerary" doesn't need to appear. Also use this to UPDATE an itinerary page already built earlier in the conversation when plans change (flight delays, weather, swapped days, cancelled bookings).
directory-map
Maps any directory tree into a structured, agent-readable taxonomy. Use this skill whenever the user wants to understand, document, or index a folder or codebase — including requests like "/directory-map", "map this project", "create a project index", "generate a directory overview", "index this repo", "help me understand what's in this folder", "create a DIRECTORY_MAP", or "build an index of this directory". Works on any language, stack, or project type. Produces three outputs: DIRECTORY_MAP.md (human-readable taxonomy), update-index.py (automated re-indexer), and index.json (machine-readable snapshot with an AgentIngress XML block for LLM context injection).
khalil-zero-cost-stack
Use when building or extending an internal business/operations app — bookings, clients, stock, jobs, invoices, appointments — that must run on free hosting with no database and no monthly bill, or when porting the React SPA + single serverless function + spreadsheet-as-database architecture to a new project. Also use when adding roles, public one-time client links, document generation, or a spreadsheet schema change to such an app.
share-live
Turn what you just built into a link you can send someone, in about a minute. Use when the user says share this, send it to someone, give me a link, put it online, show my client, demo this, or asks how to let another person open what was just built. Also use when a prototype is finished and the obvious next step is showing it to a human who is not sitting at this machine.
share-live
Get a shareable link to what you just built, right now, without picking a host or configuring anything. Use when the user says share this, send it to someone, give me a link, show my client, demo this, or needs another person to open it within the next few minutes. Publishes to Fine Structure and requires an account, which the skill states up front. If the user wants to choose their own host, or is doing a real production launch, use ship-live instead.
framer-import
Import (clone) any live Framer site into a self-contained, routed static site and deploy it to Vercel (or any static host) — then edit it by prompt and re-deploy. Use when someone wants to take a Framer site they like (their own or a template they've published), own the code, host it themselves, make changes in plain language, and ship again. Wraps the bundled FramerExport engine and works around its single-page / CDN-linked limitations, and pairs with the `framer-agent-api` skill for the editing half of the loop.
canvas-game-publishing
Architecture guidance and publishing checklists for porting Canvas-based HTML5 games to Chinese mini game platforms (WeChat, Douyin), Web, and mobile app stores. Covers the Platform adapter pattern used to keep game core platform-agnostic.
centinela-malware
Defiende un sitio o aplicación propia contra malware, webshells, compromiso de la cadena de suministro y código inyectado — y verifica cada defensa EJECUTÁNDOLA, no leyendo configuración. Cubre dependencias y secretos en el historial, integridad del artefacto desplegado, subidas de archivos, señales de intrusión, la máquina de desarrollo como perímetro, y un plan de respuesta generado y ensayado. Úsala cuando el usuario diga "malware", "me hackearon", "código raro en el sitio", "webshell", "revisa si estoy comprometido", "seguridad del servidor", "cadena de suministro", "dependencias maliciosas", "protege mi sitio", o al establecer defensas recurrentes tras un despliegue. Para el blindaje estático del perímetro (cabeceras, CORS, rate limiting, respaldo) usa escudos-de-borde; ésta cubre lo adversarial y lo recurrente.
ship-live
Get a project production ready and deployed to a host you choose. Use when the user asks which host to use, whether the project is ready to deploy, or names Netlify, Vercel, Cloudflare Pages, GitHub Pages, Railway, Render or Fly. Runs a preflight that finds what only works on localhost (hardcoded localhost calls, keys in the client bundle, a tracked .env, no SPA fallback) and a postflight that opens the deployed URL and proves it renders. If the user just wants a shareable link fast and does not want to pick a host, use share-live instead.
custom-domain
Point a custom domain at an already-deployed site, end to end: add the domain at the host, create the DNS records at the registrar, fix the settings that break silently when the address changes (auth authorized domains, OAuth redirect URIs, captcha/App Check domain lists, CORS and CSP allowlists), move the site's canonical URL, wait out certificate issuance, and add the www redirect. Use this whenever the user says they bought, registered, or own a domain; whenever they ask to hook up, connect, point, attach, set up, or "use my own" domain, URL, or address for a site; whenever they mention DNS records, nameservers, A/CNAME/TXT records, SSL or HTTPS not working on a new domain, or a domain stuck "pending", "not verified", or "needs setup"; and whenever a site currently lives on a platform subdomain (*.web.app, *.pages.dev, *.vercel.app, *.netlify.app, *.github.io) and they want it somewhere nicer. Also use it when a domain "works but login broke" or "shows the wrong URL in Google" after a move.
astro
Skill for building with the Astro web framework (v6+). Covers component authoring, islands architecture (client and server islands), content collections with loaders, actions, sessions, view transitions, middleware, on-demand rendering (SSR), adapters, and project configuration. Use when the user works with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, server islands, actions, view transitions, deploying an Astro project, or upgrading Astro.
self-ops
Operate the Agent Keyboard deployment you are running on — logs, secrets, machine status, deploys, Supabase auth config. Use when the owner asks about the server itself, deploys, secrets, boot problems, or anything ops-shaped (only meaningful on the site whose repo IS agent-keyboard).
vibe-deploy
Prepares a vibe-* project for deployment to 7 platforms: Railway, Render, Fly.io, Heroku, Vercel, Netlify, GitHub Pages. Detects stack automatically (FastAPI, Express, Next.js, Django, React, Vue, static). Patches source files (port binding to $PORT, adds /health endpoint, production CORS). Generates platform config files scoped per service — backend, web, worker. Inlines non-secret env vars directly in config files per service. Links database connections using platform-native syntax. Generates ENV_SETUP.md with per-service CLI commands for secrets only. Handles background workers and cron services if the project requires them. Optionally generates GitHub Actions CI/CD workflow. Produces DEPLOY.md step-by-step checklist. Triggers: deploy: railway, deploy: render, deploy: fly, deploy: heroku, deploy: vercel, deploy: netlify, deploy: github-pages.
02-hosting-choice
依照 spec 決定網站放在哪裡、要不要後端、金流怎麼接
launch-checklist
Validates full deployment readiness beyond code, checking infrastructure, Docker configuration, Kubernetes manifests, environment config, monitoring, security headers, and pipeline status. Use when launching, deploying to production, release readiness, go-live, deployment check, pre-launch, shipping to prod, or when preparing for production deployment.
nuxt-sanity
@nuxtjs/sanity module integration best practices for Nuxt 3 and Nuxt 4 apps connected to Sanity CMS (there is no separate `@sanity/nuxt` package). Covers useSanityQuery, useLazySanityQuery, useSanity, SanityImage, SanityContent (Portable Text), visual editing / live preview with stega, TypeScript typegen, named clients, and Nitro server routes. Also covers the Display Starter architecture with Netlify-cached server routes, preview-switch composables, Netlify CDN caching, and cache tag invalidation. Use when the user mentions @nuxtjs/sanity, nuxt-sanity, useSanityQuery, SanityImage in Nuxt, or is building a Nuxt app that fetches data from Sanity.
anti-slop-frontend-secure
Use when writing a single-file HTML artifact or a deployable frontend that must clear security gates - safe DOM construction, a host allowlist, a content-security policy, no secret in the output.
frontend-slop
Use when writing a single-file HTML artifact or a deployable frontend that must clear security gates - safe DOM construction, a host allowlist, a content-security policy, no secret in the output.
github-pages-deploy-verification
Verify a GitHub Pages (or any CDN-fronted) deploy actually serves new content. Poll on a marker that did not exist pre-deploy; avoid sleep-and-curl chains the agent harness blocks.
stale-deploy
Verify a GitHub Pages (or any CDN-fronted) deploy actually serves new content. Poll on a marker that did not exist pre-deploy; avoid sleep-and-curl chains the agent harness blocks.
deliver-and-scale
交付三档产品（网站 → 自动化 → 完整 AI 系统），并把每一档都技能化。当用户拿下了客户要交付、或想从单次项目升级到月费/系统时使用。
deployment-readiness
Prepare a managed application for its configured deployment target by adding missing deploy configuration, a deploy script, and `.aidd/deployment.md`; never deploy it. Use for deployment-readiness or deploy-configuration requests.
coupang-product-search
coupang-mcp 서버를 통해 쿠팡 상품 검색, 로켓배송 필터, 가격대 검색, 상품 비교, 베스트 상품, 골드박스 특가를 조회한다.
ship-site
Website shipping discipline — how every static site gets packaged, versioned, and deployed without overwriting live work. Use whenever finishing, packaging, zipping, or deploying any website or microsite; whenever the user says "ship it", "deploy", "push it live", "give me a zip", or "put it on Netlify". Prevents deploy-sync disasters that wipe live sites.
deploy-preview
Cron-scheduled probe. Scans open issues with non-null pr_url, finds deploy preview URLs (Vercel/Netlify/Cloudflare Pages/GitHub Pages) in PR body+comments, emits deploy_preview events on the ledger so dev-quest's FOCUS pane can show a 'Preview ready' badge.
astro-development
End-to-end Astro architecture and implementation for sites and light-to-medium web apps. Use when creating or auditing an Astro project, running Astro CLI commands, adding pages, content collections, React/shadcn islands, Actions, sessions, endpoints, middleware, adapters, Cloudflare Workers deployment, or choosing static versus on-demand rendering. Also use for Astro-based admin dashboards, with admin-dashboard leading UX decisions and shadcn-ui leading component APIs. Not for generic native-feature questions (native-first), SEO strategy/audits (seo-website-builder), or visual direction (design-taste).
Integration detected automatically from skill content. Some results may be false positives.