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.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.