// 28 tips tagged "deployment"
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Claude can read your application code — the jobs, queues, API endpoints, scheduled tasks, and critical business logic — and generate monitoring rules that alert on the things that actually matter: failed payments, queue backlogs, stale cron jobs, error rate spikes, and slow endpoints, all tailored to your real system.
Instead of piecing together a CI pipeline from Stack Overflow snippets, tell Claude to read your project and generate a GitHub Actions workflow that actually matches your stack — the right language version, your real test commands, proper caching, and the services your tests depend on.
Instead of copying a generic Dockerfile and tweaking it for an hour, tell Claude to read your project — the package files, config, build scripts, and runtime requirements — and generate a production-ready Dockerfile that's actually tailored to what your app needs.
Tell Claude to add /health and /ready endpoints that check your app's vital signs at runtime — database connectivity, Redis availability, queue worker status, disk space, and external service reachability — so load balancers and monitoring tools know when something breaks.
Tell Claude to create a startup validation script that checks every requirement before your app runs — missing env vars, unreachable databases, wrong PHP/Node versions, missing extensions, and invalid config — so you get clear errors at boot instead of cryptic failures at runtime.
Tell Claude to read your application's dependencies, runtime, build steps, and config, then generate a Dockerfile that matches — multi-stage builds, proper layer caching, non-root user, and only the files your app actually needs, all derived from the project itself.
Describe your infrastructure in plain English — "I need a VPC with public and private subnets, an RDS instance, and an ECS cluster" — and Claude writes the Terraform HCL, checks for common misconfigurations, and explains the resource dependencies.
Tell Claude to read your Dockerfile, environment variables, port config, and health check endpoints, then generate properly structured Kubernetes deployment, service, and ingress manifests — so your k8s config matches what your app actually needs.
Tell Claude to add feature flag checks around new or risky code — it reads your feature flag library or creates a simple one, wraps the feature with toggle logic, adds the flag to your config, and preserves the old code path so you can roll back instantly.
Tell Claude to read your application's routes, static assets, and API paths, then generate an nginx or Apache config that handles everything correctly — reverse proxying, SSL, static file serving, and URL rewrites, all matching what your app actually needs.
When something works locally but breaks in staging, ask Claude to compare your config files, environment variables, and runtime settings across environments — it spots the mismatches that cause environment-specific failures.