What problem does it solve? Writing correct Dockerfiles and Compose configurations involves many subtle decisions around multi-stage builds, networking, volumes, secrets, and security hardening, and mistakes lead to bloated images, leaked credentials, or broken local environments. ## Core Features & Use Cases - Compose Stack Templates: Standard web app stacks with Postgres, Redis, and Mailpit, including healthchecks, dependency ordering, and dev/prod override files. - Security Hardening: Non-root users, pinned image tags, read-only filesystems, capability dropping, and proper secret management via env files or Docker secrets. - Hardened Installer Test Harnesses: Isolated container patterns for testing CLI installers across Linux distributions with read-only mounts, tmpfs workspaces, and no-network defaults, plus honest guidance on macOS and Windows platform boundaries. - Use Case: When setting up a new Node.js project, apply the multi-stage Dockerfile and Compose override patterns to get hot-reload development and a minimal production image from one configuration. ## Quick Start Ask the AI to create a production-hardened Dockerfile and docker-compose.yml for a Node.js web app with Postgres and Redis.