docker-project-foundations
Skill1 starsChanged 14 days agoMITView on GitHub
Use this skill when setting up, initializing, or Dockerizing a project, even if the user doesn't explicitly mention Docker but describes a need for containerized local development, adding a database or cache dependency, or running services without host-level installs. Covers Dockerfile, compose.yaml, and .dockerignore creation with Docker best practices.
- Reads credentials
- Installs packages
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- docker/skillsedited, first seen Nov 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- docker/skills★ 63590% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 8 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Do not use this skill when:
- Distinctive: line 36
When Dockerizing a project, always produce all three:
- Very specific: line 49
Use the actual config path if the project keeps it elsewhere.
- Distinctive: line 65
When a project needs a database (Postgres, MySQL, MongoDB), cache (Redis, Memcached), queue (RabbitMQ, Kafka), or any other infrastructure …
- Distinctive: line 69
Use official Docker images from Docker Hub for these services.
- Very specific: line 75
Put all three files at the project root unless there is a clear multi-service layout that justifies a docker/ subdirectory.
- Distinctive: line 76
Ensure the initial setup can build and start locally with one command path.
- Distinctive: line 78
Keep unauthenticated datastores on the Compose network instead of publishing their ports.
- Very specific: line 79
If a development-only credential fallback enables one-command startup, label it clearly and document a .env override.
- Distinctive: line 80
Use Compose services for local databases, caches, and queues instead of host installs.
- Distinctive: line 81
Keep the first scaffold simple.
- Very specific: line 87
Keep a single Dockerfile that supports both via build stages and build arguments when possible.
- Very specific: line 91
Place Dockerfile at the project root (or in a docker/ subdirectory if the project has multiple services).
- Very specific: line 92
Place compose.yaml at the project root.
- Very specific: line 93
Place .dockerignore at the project root, next to the Dockerfile.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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. Seeassets/Dockerfile.simple.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.
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, non-root execution, and image hardening, use
docker-build-strategies. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

