// 15 tips tagged "deployment"
Describe your server setup in plain English and let Claude write a complete, idempotent Ansible playbook — modules, handlers, roles, and all the boilerplate you'd otherwise look up.
Bloated Docker images slow CI, increase attack surface, and cost money — paste your Dockerfile and ask Claude to audit it for quick wins.
Every production app needs a health check endpoint for load balancers and container orchestrators — Claude scaffolds a robust one in seconds.
Writing Ansible YAML by hand is repetitive and easy to get wrong. Describe your infrastructure requirements in plain English and let Claude generate the playbook.
Ask Claude to write a GitHub reusable workflow for your shared CI steps — lint, static analysis, tests, caching, and coverage — so every repo calls one central definition instead of duplicating YAML.
Describe your stack and build requirements and let Claude write a proper vite.config.ts — path aliases, dev proxies, chunk splitting, source maps, and tree-shaking all configured correctly.
Describe your stack and hosting setup and let Claude write a production-ready Nginx or Caddy config — rate limiting, cache headers, SPA routing, and proxy settings all handled correctly.
mosh (mobile shell) keeps your SSH connection to a remote Claude Code server alive through network switches, laptop sleep, and wifi drops — where regular SSH would silently die.
Paste your bundle analysis output and Claude will identify the biggest wins — duplicate dependencies, oversized imports, and code-splitting opportunities.
Describe your cloud infrastructure in plain English and let Claude write the Terraform — modules, variables, outputs, and all.
Describe your full stack in plain English and Claude will write a production-ready docker-compose.yml with all services wired up correctly.
Kubernetes YAML is verbose and unforgiving — describe what you need in plain English and let Claude write the manifests.