What problem does it solve? Writing secure, reproducible Dockerfiles and Compose stacks is error-prone: developers commonly ship root containers, :latest tags, leaked secrets, and untested installers. This Skill provides reviewed patterns and hardening rules for containerized development. ## Core Features & Use Cases - Compose Stack Patterns: Standard web app stacks with Postgres, Redis, and Mailpit, including healthchecks, named volumes, and dev/prod override files. - Dockerfile Hardening: Multi-stage builds, non-root users, pinned image tags, read-only filesystems, capability dropping, and secret management via Compose secrets. - Isolated Installer Testing: Hardened container harnesses for testing CLI installers across Linux distributions, with read-only mounts, tmpfs workspaces, no network, and explicit platform boundaries for macOS and Windows. - Use Case: When reviewing a project's docker-compose.yml, apply these patterns to bind ports to localhost, add database healthchecks, move secrets out of the file, and split dev and production configurations. ## Quick Start Review my Dockerfile and docker-compose.yml using the docker patterns skill and suggest security and structure improvements.