dev-docker/SKILL.md
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
npx skillsauth add paulund/ai dev-dockerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
service_healthy for services with healthchecks, service_completed_successfully for migration jobs| Topic | Reference | Load When |
|-------|-----------|-----------|
| Healthchecks | references/healthchecks.md | Configuring healthcheck commands, timing, depends_on conditions |
| Networking | references/networking.md | Custom networks, service DNS, port exposure vs publishing |
| Volumes | references/volumes.md | Named volumes, bind mounts, tmpfs, sharing between services |
| Environment | references/environment.md | .env files, variable substitution, secrets, env_file |
| Profiles | references/profiles.md | Optional services (Mailpit, Adminer) toggled with --profile |
| Override Files | references/override.md | Per-environment compose files for dev, CI, and production |
service_healthy in depends_on whenever a healthcheck is defined on the target serviceservice_completed_successfully for one-off jobs (migrations, seed scripts)expose for internal ports, ports only for services that need host access.env and docker-compose.override.yml to .gitignore.env.example and docker-compose.override.yml.example as templatesservice_started for databases — a running container is not a ready database.env or Docker secretsdevelopment
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
development
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
development
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
development
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.