Docker Compose

**Verdict:** A strong, concise best-practices skill for Docker Compose that focuses on real-world pitfalls and safe workflows. It is particularly useful for intermediate users who already know basic Compose syntax and want to avoid subtle errors in production. **Strengths** - Correctly distinguishes container start from service readiness and recommends `healthcheck` + `depends_on: condition: service_healthy` for more robust startup ordering. - Accurately warns about `docker compose down -v` and the risk of irreversible data loss, clarifying the behavior of named vs. anonymous volumes. - Promotes use of `.dockerignore` to avoid large/unsafe build contexts (e.g., excluding `.git`, `node_modules`, `.env`, logs, build artifacts). - Encourages clean environment-specific workflows through `docker-compose.override.yml`, additional override files (e.g., prod), and profiles for optional services. - Explains environment variable precedence in the correct order and recommends `docker compose config` for debugging the final merged configuration. **Notable Risks / Limitations** - The guidance around `deploy: resources: limits:` for development is potentially misleading: in non-Swarm `docker compose` workflows, the `deploy` section is typically ignored, so these resource limits may not actually be enforced. Users relying on this to catch memory issues during local development could have a false sense of safety. - Some recommendations (e.g., `depends_on` with `condition: service_healthy`) depend on the specific Compose implementation and version; users should verify support against their Docker/Compose version. - The skill is oriented toward configuration quality and operational safety, not toward generating complete Compose files from scratch or covering every feature of the Compose spec. **Recommended Scenarios** - As a checklist or reviewer when you are writing or refactoring `docker-compose.yml` for real applications. - For teams standardizing Docker Compose practices across development and production, especially around volumes, overrides, and env handling. - As an onboarding reference for developers who know Docker basics but need to understand the non-obvious behavior and footguns of Docker Compose in day-to-day use.