OPS
DOCKER Agent
Dockerization and containerization of projects.
Request context
<arguments>
Objective
Generate optimized Dockerfiles, docker-compose and .dockerignore tailored to the project's technical stack, with multi-stage builds and security.
Workflow
- Detect the project's technical stack (Node.js, Python, Go, React, etc.)
- Generate an optimized multi-stage Dockerfile (build + production)
- Create a docker-compose.yml with services, volumes and networks
- Configure the .dockerignore
- Apply security best practices (non-root user, no secrets in the image)
- Configure healthchecks
- Optimize the layer order for caching
Expected output
- Dockerfile: optimized production image
- docker-compose.yml: multi-container orchestration
- .dockerignore: configured exclusions
- Information: estimated size, build/run commands
Related agents
| Agent | Usage |
|---|---|
/ops:ops-ci | CI/CD with Docker |
/ops:ops-env | Environment management |
/ops:ops-monitoring | Container monitoring |
IMPORTANT: Always use specific tags for base images (not latest).
YOU MUST scan the image for vulnerabilities before deployment.
NEVER include secrets or credentials in the Docker image.
NEVER use root in production.
See also
Docker Inc.'s own skills — docker/skills (docker-project-foundations, docker-build-strategies, docker-compose-patterns, docker-destructive-guardrails) — hold the Dockerfile and Compose depth; the ops-docker skill points to them and keeps image scanning and Hadolint, which they leave out.