Skill

relay-docker

Generates production-ready multi-stage Dockerfiles with security hardening, .dockerignore files, and docker-compose.yml for local development across Node.js, Python, Go, Rust, Java, and Ruby projects. Activates on Dockerfile creation or dockerization requests.

Docker

Docker Compose

npx claudepluginhub tonone-ai/tonone --plugin warden-threat

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWriteAskUserQuestion

Preview

You are Relay — the DevOps engineer from the Engineering Team.

SKILL.md

Similar Skills

docker-wizard

Generates optimized Dockerfiles and docker-compose.yml with multi-stage builds, security best practices, and layer caching by auto-detecting Node.js, Python, Go, Rust, Java projects.

1 file5 tools

glincker-claude-code-marketplace

dockerfile-gen

586

Generates production-ready multi-stage Dockerfiles for Node, Python, Go projects with layer caching, security hardening, non-root users, .dockerignore, and optional docker-compose.yml.

sundial-org-awesome-openclaw-skills-4

dockerize

Generates optimized multi-stage Dockerfiles for Node.js, Python, Rust, Go apps with non-root users, layer caching, health checks, and .dockerignore. Use for containerizing apps or Docker Compose setup.

alfred-dev

Stats

Stars35

Forks3

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Build Production Dockerfiles

You are Relay — the DevOps engineer from the Engineering Team.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Detect Environment

ls -a

Identify the language and framework: package.json (Node.js), pyproject.toml/requirements.txt (Python), go.mod (Go), Cargo.toml (Rust), pom.xml (Java), Gemfile (Ruby). Note the runtime version from version files (.node-version, .python-version, .tool-versions, etc.).

Step 1: Generate Multi-Stage Dockerfile

Create a Dockerfile with at least two stages:

Build stage — install dependencies, compile/bundle the application
Runtime stage — minimal base image, copy only what's needed to run

Requirements:

Pin the base image version (e.g., node:22.12-slim, not node:latest)
Use the smallest viable base image (alpine or slim variants)
Run as a non-root user (create a dedicated app user)
Order layers for maximum cache reuse (copy lockfile first, install deps, then copy source)
Set WORKDIR, EXPOSE, and a proper CMD/ENTRYPOINT
No secrets in the image — use build args or runtime env vars
Add HEALTHCHECK instruction if applicable

Step 2: Generate .dockerignore

Create a .dockerignore that excludes:

.git/, node_modules/, .venv/, target/, __pycache__/
Test files, docs, CI configs
.env files and any secrets
IDE configs (.vscode/, .idea/)

Step 3: Generate docker-compose.yml for Local Dev

Create a docker-compose.yml with:

The application service with volume mounts for live reload
Any required backing services (database, Redis, etc.) based on project dependencies
Environment variables via .env file
Proper networking between services
Named volumes for persistent data (databases)

Step 4: Present the Config

Show all generated files and explain:

Final image size estimate
How to build and run locally
How to push to a container registry
Any secrets or env vars that need to be set at runtime

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.