Dockerizing a project
Dockerizes a project from scratch with a .dockerignore, a multi-stage Dockerfile and a compose.yaml that runs databases and caches as Compose services instead of host installs. Use when a project has no Docker setup or needs a local database or cache.
docker-project-foundations- Author
- Docker
- Source
- docker/skills/skills/docker-project-foundations @ caeee20
- License
- Apache-2.0 · Copyright 2026 Docker, Inc.
About this skill
What it does
The skill gives a project its first Docker setup, always as three files, usually at the root: .dockerignore first, then a Dockerfile, then a compose.yaml for local development. Even the first draft keeps a baseline: a multi-stage build when there is a build or install step, a base image pinned to a version (node:22-slim), dependency manifests copied before the source and a non-root USER in the final stage.
Databases, caches and queues become Compose services from official images; the skill forbids telling the user to brew install postgres or apt install redis. Application ports are published on 127.0.0.1 by default, datastores without authentication stay on the Compose network, and a database that host tools need is published on 127.0.0.1 only. For a private npm registry, .npmrc is excluded at every depth and passed in as a BuildKit secret.
The folder ships assets/Dockerfile.simple, a four-stage Node.js template (deps, dev, build, production); assets/compose-dev.yaml, an app with Postgres, Redis, health checks, a live-reload bind mount and a named volume; a .dockerignore template; references/project-structure.md on multi-service layouts; scripts/verify-setup.sh, which checks that the three files exist and runs docker compose config --quiet; a verification checklist and eval prompts.
When to use it, and when not
Use it to Dockerize a project that has no Docker setup, or to add a database or cache without installing it on the host. It needs Docker 20.10+ and Compose v2.
Skip it when the user does not want Docker or the project already has a working setup.
How to run it
The install command below puts the whole folder in place. The agent picks the skill up by its description; to call it yourself:
- Claude Code:
/docker-project-foundations, or ask for the skill by name. - Codex:
$docker-project-foundations. - Cursor: type
/in the Agent chat and pickdocker-project-foundations.
Example: /docker-project-foundations Dockerize this Express app with Postgres for local development. One command should bring everything up.
The script runs from the project root: bash "<skill-dir>/scripts/verify-setup.sh".
How it differs from similar skills
The pack splits the work: this skill writes the scaffold and keeps it simple, Dockerfile build strategies tunes the image afterwards, and Docker Compose patterns takes over the stack; install them together. Dockerfile review from our catalog writes or reviews a Dockerfile and gives no guidance on Compose or service dependencies. Prototype to production hardens an app before launch — error handling, validation, config, tests — and does not touch containers.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/docker-project-foundations/SKILL.md https://anymodel.org/en/skills/docker/docker-project-foundations/SKILL.md -o ~/.claude/skills/docker-project-foundations/LICENSE https://anymodel.org/en/skills/docker/docker-project-foundations/LICENSE -o ~/.claude/skills/docker-project-foundations/agents/openai.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/agents/openai.yaml -o ~/.claude/skills/docker-project-foundations/assets/Dockerfile.simple https://anymodel.org/en/skills/docker/docker-project-foundations/assets/Dockerfile.simple -o ~/.claude/skills/docker-project-foundations/assets/compose-dev.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/assets/compose-dev.yaml -o ~/.claude/skills/docker-project-foundations/assets/dockerignore-example https://anymodel.org/en/skills/docker/docker-project-foundations/assets/dockerignore-example -o ~/.claude/skills/docker-project-foundations/checks/verification.md https://anymodel.org/en/skills/docker/docker-project-foundations/checks/verification.md -o ~/.claude/skills/docker-project-foundations/evals/docker-project-foundations.md https://anymodel.org/en/skills/docker/docker-project-foundations/evals/docker-project-foundations.md -o ~/.claude/skills/docker-project-foundations/references/project-structure.md https://anymodel.org/en/skills/docker/docker-project-foundations/references/project-structure.md -o ~/.claude/skills/docker-project-foundations/scripts/verify-setup.sh https://anymodel.org/en/skills/docker/docker-project-foundations/scripts/verify-setup.sh -o ~/.claude/skills/docker-project-foundations/skill.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/skill.yaml && chmod +x ~/.claude/skills/docker-project-foundations/scripts/verify-setup.sh
curl -fsSL --create-dirs -o ~/.agents/skills/docker-project-foundations/SKILL.md https://anymodel.org/en/skills/docker/docker-project-foundations/SKILL.md -o ~/.agents/skills/docker-project-foundations/LICENSE https://anymodel.org/en/skills/docker/docker-project-foundations/LICENSE -o ~/.agents/skills/docker-project-foundations/agents/openai.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/agents/openai.yaml -o ~/.agents/skills/docker-project-foundations/assets/Dockerfile.simple https://anymodel.org/en/skills/docker/docker-project-foundations/assets/Dockerfile.simple -o ~/.agents/skills/docker-project-foundations/assets/compose-dev.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/assets/compose-dev.yaml -o ~/.agents/skills/docker-project-foundations/assets/dockerignore-example https://anymodel.org/en/skills/docker/docker-project-foundations/assets/dockerignore-example -o ~/.agents/skills/docker-project-foundations/checks/verification.md https://anymodel.org/en/skills/docker/docker-project-foundations/checks/verification.md -o ~/.agents/skills/docker-project-foundations/evals/docker-project-foundations.md https://anymodel.org/en/skills/docker/docker-project-foundations/evals/docker-project-foundations.md -o ~/.agents/skills/docker-project-foundations/references/project-structure.md https://anymodel.org/en/skills/docker/docker-project-foundations/references/project-structure.md -o ~/.agents/skills/docker-project-foundations/scripts/verify-setup.sh https://anymodel.org/en/skills/docker/docker-project-foundations/scripts/verify-setup.sh -o ~/.agents/skills/docker-project-foundations/skill.yaml https://anymodel.org/en/skills/docker/docker-project-foundations/skill.yaml && chmod +x ~/.agents/skills/docker-project-foundations/scripts/verify-setup.sh
foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml','assets/Dockerfile.simple','assets/compose-dev.yaml','assets/dockerignore-example','checks/verification.md','evals/docker-project-foundations.md','references/project-structure.md','scripts/verify-setup.sh','skill.yaml') { $p = Join-Path "$HOME\.claude\skills\docker-project-foundations" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/docker/docker-project-foundations/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml','assets/Dockerfile.simple','assets/compose-dev.yaml','assets/dockerignore-example','checks/verification.md','evals/docker-project-foundations.md','references/project-structure.md','scripts/verify-setup.sh','skill.yaml') { $p = Join-Path "$HOME\.agents\skills\docker-project-foundations" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/docker/docker-project-foundations/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/docker/docker-project-foundations/SKILL.md
SKILL.md
Docker Project Foundations
Overview
This skill guides you in Dockerizing a project from scratch. It focuses on creating the initial Docker file set, choosing a sane layout, and preferring containerized dependencies over host-level installs.
When to use this skill
Activate this skill when:
- A user asks you to set up, initialize, or Dockerize a project
- A project needs an initial
Dockerfile,compose.yaml, or.dockerignoreand does not have one - A user wants to add a service dependency (database, cache, message queue) to a project
- A user asks how to run or develop a project locally and Docker is available
Do not use this skill when
Do not use this skill when:
- The user explicitly wants to avoid Docker
- The project already has a mature Docker setup and only needs minor edits
- The main task is optimizing an existing
Dockerfile - The main task is editing or debugging an existing Compose stack
Core guidance
Always create these three files
When Dockerizing a project, always produce all three:
.dockerignore— Create this first so the initial build context is small and safe. Seeassets/dockerignore-examplefor a reference.Dockerfile— Create a working starter image definition that the project can build and run with. Start fromassets/Dockerfile.simpleand keep its baseline, even for a first scaffold:- multi-stage build (dependencies, build, and a separate runtime stage) whenever the project has a build or dependency-install step;
- base image pinned to a specific version (e.g.
node:22-slim), neverlatest; - dependency manifests (
package.json+ lockfile) copied before the source for layer caching; - a non-root
USERset in the final stage beforeCMD/ENTRYPOINT.
compose.yaml— Create a local development stack that includes the application service and any required dependencies. Seeassets/compose-dev.yaml.
npm registry credentials
- Exclude
.npmrcat every depth with**/.npmrcin.dockerignore; otherwise a broad source copy can persist credentials in image layers. - The Node.js starter mounts
npmrcas a BuildKit secret for bothnpm cisteps. Public-package builds need no secret. For private registries, pass the config explicitly:
Use the actual config path if the project keeps it elsewhere. Never copy the credential file or pass its values throughDOCKER_BUILDKIT=1 docker build --secret id=npmrc,src="$HOME/.npmrc" .ARGorENV. Dependency scripts run during installation can access the mounted secret; use trusted dependencies and a least-privilege registry token. - For private-registry builds through Compose, add this optional override as
compose.npm.yamlalongside the starter'scompose.yaml:
Build withservices: app: build: secrets: - npmrc secrets: npmrc: file: ${NPMRC_PATH:?Set NPMRC_PATH to your npm config file}NPMRC_PATH="$HOME/.npmrc" docker compose -f compose.yaml -f compose.npm.yaml build. This grants build-time access only, not a runtime secret. Public-package builds should omit the override so no credential file is required.
Prefer Dockerized dependencies over host installs
When a project needs a database (Postgres, MySQL, MongoDB), cache (Redis, Memcached), queue (RabbitMQ, Kafka), or any other infrastructure service:
- Always define it as a service in
compose.yamlinstead of telling the user to install it on the host. - Never suggest
brew install postgres,apt install redis, or similar host-level installs for development dependencies. - Use official Docker images from Docker Hub for these services.
- Configure services with environment variables, not config files baked into images.
Bootstrap checklist
- Name the file
compose.yamlrather than legacy Compose filenames. - Put all three files at the project root unless there is a clear multi-service layout that justifies a
docker/subdirectory. - Ensure the initial setup can build and start locally with one command path.
- Bind published application ports to loopback by default. Widen the host address only when another device must reach the development service.
- Keep unauthenticated datastores on the Compose network instead of publishing their ports. If local host tools require database access, publish only to loopback.
- If a development-only credential fallback enables one-command startup, label it clearly and document a
.envoverride. - Use Compose services for local databases, caches, and queues instead of host installs.
- Keep the first scaffold simple; defer detailed image optimization and advanced Compose tuning to the owning skills. "Simple" never means dropping the Dockerfile baseline above (multi-stage, pinned base, non-root
USER).
Development vs production
- Development: Use bind mounts for live reload, publish application ports on loopback by default, and enable verbose logging. Keep unauthenticated datastores on the Compose network; publish a datastore port only on loopback when local host tools require it.
- Production: Use multi-stage builds, copy only built artifacts, do not mount source code, minimize image layers, set appropriate resource limits.
- Keep a single
Dockerfilethat supports both via build stages and build arguments when possible.
File placement
- Place
Dockerfileat the project root (or in adocker/subdirectory if the project has multiple services). - Place
compose.yamlat the project root. - Place
.dockerignoreat the project root, next to theDockerfile.
Related skills
- For Dockerfile optimization, cache strategy, advanced non-root hardening, and image hardening, use
docker-build-strategies. The starter baseline above (including a non-rootUSER) still applies here. - For service dependencies, health checks, overrides, volumes, networks, and Compose debugging, use
docker-compose-patterns. - For destructive Docker CLI commands (
docker system prune,docker rm -f, image/network/builder pruning) and a cross-product index of destructive-command guardrails, usedocker-destructive-guardrails.
References
references/project-structure.md— Detailed guidance on Docker project file organization, naming conventions, and multi-service layouts.
Assets
assets/dockerignore-example— A comprehensive.dockerignorefor a typical project.assets/compose-dev.yaml— A development-oriented Compose file with Dockerized dependencies.assets/Dockerfile.simple— A basic multi-stage Dockerfile following best practices.
Scripts
scripts/verify-setup.sh— Checks that required files exist in the current directory and validates itscompose.yaml. Run it from the project root, with the script path resolved under this skill's directory:
Replacebash "<skill-dir>/scripts/verify-setup.sh" [--help]<skill-dir>with the absolute path of the folder that contains thisSKILL.md; thescripts/path is relative to that folder, not to the project. Do not change into the skill directory first: the script checks the current directory. If the skill directory cannot be resolved, check that.dockerignore,Dockerfile, andcompose.yamlexist in the project root, then rundocker compose config --quiet. Exit status is0when verification succeeds or help is requested,1when required files are missing or the Compose configuration is invalid, and2for invalid arguments.
Checks
checks/verification.md— Detailed verification checklist for manual review.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel