dockerfile-generator_skill

Overview

This skill generates production-ready Dockerfiles tailored to your project's language and framework, applying multi-stage builds, layer caching, and security best practices. It detects project type, creates an optimized Dockerfile and .dockerignore, and can suggest a docker-compose.yml and build/run commands. The output is focused on smaller images, faster builds, and safer runtime configuration.

How this skill works

The skill scans project files (package.json, requirements.txt, go.mod, pom.xml, Cargo.toml, etc.) to identify language and framework. It then emits a multi-stage Dockerfile optimized for caching, minimal runtime images, and non-root execution, plus a .dockerignore to shrink build context. Optional outputs include a docker-compose template and concrete build/run commands with environment and volume suggestions.

When to use it

• When you ask “create Dockerfile”, “dockerize my app”, “containerize”, or “docker setup”
• When you want a production-ready Dockerfile with multi-stage builds
• When you need optimized layer caching to speed CI/CD builds
• When you want security best practices applied (non-root, pinned base images)
• When you need a docker-compose scaffold for local development

Best practices

• Use multi-stage builds to keep runtime images minimal and exclude dev dependencies
• Copy dependency manifests first and install to leverage layer caching
• Pin base image versions (avoid :latest) and prefer slim/alpine variants when compatible
• Run processes as a non-root user and minimize installed packages
• Combine RUN steps and clean caches in the same layer to reduce image size
• Include a .dockerignore to shrink build context and speed builds

Example use cases

• Generate an optimized Dockerfile for a Node.js/Next.js app with separate build and runtime stages
• Create a minimal Go or Rust production image using a builder stage and scratch/alpine runtime
• Produce a Python/Django or Flask Dockerfile with dependency stage, non-root user, and gunicorn setup
• Create a Spring Boot Dockerfile that caches dependency downloads and copies only the final jar into a lightweight JRE image
• Provide a docker-compose.yml connecting app and Postgres for local dev and CI integration