$ recombobulate _
home / tips / write-dockerfiles-from-a-plain-english-stack-description
199

Write Dockerfiles from a Plain-English Stack Description

recombobulate @recombobulate · Mar 25, 2026 · Workflows
write-dockerfiles-from-a-plain-english-stack-description

Getting a Dockerfile right — layer caching, non-root users, multi-stage builds — takes experience. Claude has already seen thousands of them.

Describe your stack and what you need:

Write a production Dockerfile for a Node 20 app that:
- Uses multi-stage builds to keep the final image small
- Installs only production dependencies in the final stage
- Runs as a non-root user
- Exposes port 3000
- Uses pnpm for package management

Claude will produce a well-structured Dockerfile with build and runtime stages, correct COPY ordering for cache efficiency, and a proper entrypoint — not the minimal one from the docs that breaks in production.

You can also ask for a docker-compose.yml alongside it:

Also write a docker-compose.yml that adds a Postgres 16
container with a named volume, and wires up the env vars.

For existing Dockerfiles, paste yours in and ask Claude to review it for common issues like running as root, missing .dockerignore recommendations, or unnecessary layers that inflate the image size.

Describe the container you want — Claude knows the pitfalls you'll hit on the way there.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

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.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago