Docker & Containerization Configurator

What it does

/dockerize is a Cursor slash command. Type it in chat to run a saved workflow: Docker & Containerization Configurator.

Creates optimized multi-stage Dockerfiles and docker-compose configurations for development and production, minimizing image size and maximizing security.

Multi-stage Dockerfile, docker-compose.yml, and production container hardening. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /dockerize for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /dockerize exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to the DevOps & Deployment Pro (devops-engineer) and Cloud Infrastructure Architect (cloud-architect) agents. Required skills: Multi-Stage Docker & Container Deployments; Terraform Infrastructure as Code (IaC).

When to use it

• Use when containerizing your application for AWS ECS, Fly.io, Railway, or Kubernetes.
• Use /dockerize when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /dockerize as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Configure next.config.ts with output: 'standalone'
2. Create multi-stage Dockerfile (deps, builder, runner stages)
3. Set up non-root security permissions and runtime environment variables
4. Generate docker-compose.yml for local multi-service development

Example usage

Type this in Cursor chat: /dockerize Create production Dockerfile for Next.js app with multi-stage build and Alpine Linux

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: Dockerfile
• Expected artifact: docker-compose.yml
• Expected artifact: .dockerignore

Best practices

• Keep the prompt specific. /dockerize Create production Dockerfile for Next.js app with multi-stage build and Alpine Linux is the shape: object, constraint, and outcome.
• Let the listed agents work in order: devops-engineer → cloud-architect.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /dockerize with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Multi-Stage Docker & Container Deployments skill that the command depends on.