Deploy and launch
Putting your site or app online, on your own domain, and keeping it running.
10 skills. Each one is plain markdown you can paste into ChatGPT, Claude, Gemini or any AI chat, or install in Claude Code or Cursor. How it works
configure-github-actions-ci
Configures a GitHub Actions workflow that installs dependencies with caching, then runs lint, type-check, tests and build on every push and pull request. Use when the user wants CI, automated tests on PRs, a build pipeline, GitHub workflows, or checks before merging.
Not yet model-tested; testing Jan 2027Deploy and launchcontainerise-app-with-docker
Packages an app into a small, secure Docker image with a multi-stage Dockerfile - pinned slim base images, cached dependency layers, a .dockerignore, a non-root user and a health check - then builds and runs it locally. Use when the user wants to dockerise an app, write a Dockerfile, shrink a huge image, or run their app in a container.
Not yet model-tested; testing Jan 2027Deploy and launchdeploy-nextjs-to-vercel
Deploys a Next.js app to Vercel with environment variables, a custom domain and preview deployments per branch. Use when the user wants to ship, host, publish or go live with a Next.js or React site on Vercel, or mentions vercel deploy, production URL or domains.
Not yet model-tested; testing Jan 2027Deploy and launchdeploy-site-to-cloudflare
Deploys a static site, single-page app or full-stack app to Cloudflare Workers with Wrangler - log in, pick static assets or a Worker, set secrets, preview, then ship - and adds storage such as KV, D1 or R2 only when needed. Use when the user wants to host on Cloudflare, deploy with wrangler, or move a site to Cloudflare Workers or Pages.
Not yet model-tested; testing Jan 2027Deploy and launchdeploy-site-to-netlify
Deploys a web project to Netlify with the Netlify CLI - check login, link or create the site, confirm build settings in netlify.toml, ship a draft preview, then promote to production. Use when the user wants to host on Netlify, publish a preview deploy, link a repo to Netlify, or fix a Netlify build setting.
Not yet model-tested; testing Jan 2027Deploy and launchlaunch-website-checklist
Takes a deployed site live on its own domain, covering DNS records, HTTPS, www redirect, security headers, Google Search Console and a final go-live checklist (links, mobile, form, 404, share preview). Use when the user wants to launch a site, connect a custom domain, or run a pre-launch checklist before going live.
Not yet model-tested; testing Jan 2027Deploy and launchset-up-custom-domain-and-dns
Connects a custom domain to a hosted site - add the domain on the host, create the right A, CNAME or nameserver records at the registrar, choose www or apex, wait for HTTPS, redirect the other version, and keep email records intact. Use when the user bought a domain on Namecheap, GoDaddy or Cloudflare and wants their site on it, or DNS is not working.
Not yet model-tested; testing Jan 2027Deploy and launchset-up-env-variables-and-secrets
Sets up environment variables and secrets safely - a .env.local that git ignores, a committed .env.example, values added on the host per environment, browser-safe prefixes only for public values, and a plan to rotate a key that leaked. Use when the user asks where to put API keys, how .env files work, or committed a secret key to git by mistake.
Not yet model-tested; testing Jan 2027Deploy and launchset-up-git-guardrails-and-pre-commit
Sets up safety rails for AI coding agents - a hook that blocks push, reset --hard, clean -f and branch -D before the agent runs them, plus Husky and lint-staged pre-commit checks for format, typecheck and tests. Use when the user wants to stop an AI from pushing or wiping work, add pre-commit hooks, set up Husky, or block dangerous git commands.
Not yet model-tested; testing Jan 2027Deploy and launchset-up-git-worktrees-and-finish-branch
Runs a feature from start to finish in its own git worktree - check for existing isolation, create an ignored worktree, install and run baseline tests - then finishes the branch by verifying tests and offering merge, pull request or keep. Use when starting isolated feature work, running parallel agents on one repo, setting up a git worktree, or finishing and cleaning up a development branch.
Not yet model-tested; testing Jan 2027