A skill your agent uses 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…
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .claude/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add docker/skills --skill docker-project-foundations -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .agents/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add docker/skills --skill docker-project-foundations -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .cursor/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add docker/skills --skill docker-project-foundations -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .gemini/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add docker/skills --skill docker-project-foundations -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .github/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add docker/skills --skill docker-project-foundations -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "docker-project-foundations" agent skill from https://github.com/docker/skills/tree/main/skills/docker-project-foundations into .opencode/skills/docker-project-foundations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docker-project-foundations", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
docker-project-foundations
GitHub stars
539
Token cost
~1.9k tokens
SKILL.md length
900 words
Files
9 (incl. scripts, references, assets)
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0
At a glance
A skill your agent uses 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…
Works in 3 steps: .dockerignore — Create this first so the… → Dockerfile — Create a working starter… → compose.yaml — Create a local…
Dockerizing a project
SKILL.md covers Overview, When to use this skill, Do not use this skill when and Core guidance, plus 5 more sections
Runs Shell scripts from its folder; calls docker, bash and npm
What it does
Docker Project Foundations is an agent skill from docker/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `assets/compose-dev.yaml` and `checks/verification.md`). Compatibility notes: Requires Docker 20.10+ and Docker Compose v2.
It sits in DevOps & Cloud, covering Containers. It works with Docker and npm. The repository describes itself as: A collection of Docker skills for AI coding agents to help them build, test, debug, and optimize containerized apps with consistent, reusable workflows. The licence is Apache-2.0.
When your agent uses it
Dockerizing a project
Even if the user doesnt explicitly mention Docker but describes a need for containerized local development
Adding a database
Cache dependency
Example prompts
“/docker-project-foundations”
Requirements
Node.js
A Bash shell
Docker
Compatibility (from SKILL.md): Requires Docker 20.10+ and Docker Compose v2.
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
1.dockerignore — Create this first so the initial build context is small and safe. See assets/dockerignore-example for a reference.
2Dockerfile — Create a working starter image definition that the project can build and run with. See assets/Dockerfile.simple.
3compose.yaml — Create a local development stack that includes the application service and any required dependencies. See…
What it can do on your machine
Read from SKILL.md and the folder at commit f791727. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
docker
bash
npm
brew
apt
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Docker 20.10+ and Docker Compose v2.
From compatibility in the SKILL.md frontmatter.
Context cost
Docker Project Foundations loads about 1.9k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 900 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~96
When it runs· the whole SKILL.md, loaded when a task matches
~1.9k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~2.7k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: warnings
The automated check found patterns that need a careful read before installing.
WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:44
- Exclude `.npmrc` at every depth with `**/.npmrc` in `.dockerignore`; otherwise a broad source copy can persist credent
WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:47
cker build --secret id=npmrc,src="$HOME/.npmrc" .
WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:61
Build with `NPMRC_PATH="$HOME/.npmrc" docker compose -f compose.yaml -f compose.npm.yaml build`. This grants build-tim
NoteMentions a .env fileSKILL.md:79
tartup, label it clearly and document a `.env` override.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/docker-project-foundations/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
docker-project-foundations
description
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.
compatibility
Requires Docker 20.10+ and Docker Compose v2.
license
Apache-2.0
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 .dockerignore and 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. See assets/dockerignore-example for a reference.
Dockerfile — Create a working starter image definition that the project can build and run with. See assets/Dockerfile.simple.
compose.yaml — Create a local development stack that includes the application service and any required dependencies. See assets/compose-dev.yaml.
npm registry credentials
Exclude .npmrc at every depth with **/.npmrc in .dockerignore; otherwise a broad source copy can persist credentials in image layers.
The Node.js starter mounts npmrc as a BuildKit secret for both npm ci steps. Public-package builds need no secret. For private registries, pass the config explicitly:bash
Use the actual config path if the project keeps it elsewhere. Never copy the credential file or pass its values through ARG or ENV. 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.yaml alongside the starter's compose.yaml:yaml
services:
app:
build:
secrets:
- npmrc
secrets:
npmrc:
file: ${NPMRC_PATH:?Set NPMRC_PATH to your npm config file}
Build with 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.yaml instead 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.yaml rather 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 .env override.
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.
Show full SKILL.md (332 more words)Show less
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 Dockerfile that supports both via build stages and build arguments when possible.
File placement
Place Dockerfile at the project root (or in a docker/ subdirectory if the project has multiple services).
Place compose.yaml at the project root.
Place .dockerignore at the project root, next to the Dockerfile.
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, use docker-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 .dockerignore for 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 its compose.yaml. Run it from the project root, with the script path resolved under this skill's directory:bash
Replace <skill-dir> with the absolute path of the folder that contains this SKILL.md; the scripts/ 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, and compose.yaml exist in the project root, then run docker compose config --quiet. Exit status is 0 when verification succeeds or help is requested, 1 when required files are missing or the Compose configuration is invalid, and 2 for invalid arguments.
Checks
checks/verification.md — Detailed verification checklist for manual review.
Docker Project Foundations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Docker Project Foundations compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Docker Project Foundations this skilldocker/skills
A skill your agent uses when creating, modifying, or debugging Docker Compose configurations, even if the user just says they need to wire services together, add a database to their stack, or set up…
A skill your agent uses when writing, reviewing, or optimizing Dockerfiles, even if the user just says their image is too large, their build is slow, or they need to harden a container for production.
A skill your agent uses when creating or editing an agent.yaml (or .yml/.hcl) configuration file for Docker Agent (cagent), including defining agents, models/providers, built-in or MCP toolsets…
A skill your agent uses when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat), distributing an agent via an OCI registry with docker agent share, or measuring…
A skill your agent uses when authoring, planning, or running a declarative sbxenv.yaml file for Docker Sandboxes (sbx env create/run/plan/exec/rm), even if the user just says they want to "check in…
A skill your agent uses when authoring, validating, packaging, signing, or composing a Docker Sandboxes kit spec.yaml (sbx kit add/inspect/pack/pull/push/sign/validate/verify), even if the user just…
A skill your agent uses 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…. Docker Project Foundations is an agent skill from docker/skills, published by the product's own GitHub organization. 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.
When should I use Docker Project Foundations?
Docker Project Foundations fits situations like: dockerizing a project; even if the user doesnt explicitly mention Docker but describes a need for containerized local development; adding a database; cache dependency.
How do I install Docker Project Foundations in Claude Code?
Run `npx skills add docker/skills --skill docker-project-foundations -a claude-code`. Or copy the skill folder (skills/docker-project-foundations in docker/skills) into .claude/skills/docker-project-foundations in your project. Claude Code loads it when a task matches its description.
How do I install Docker Project Foundations in Codex?
Run `npx skills add docker/skills --skill docker-project-foundations -a codex`. Or copy the skill folder (skills/docker-project-foundations in docker/skills) into .agents/skills/docker-project-foundations in your project. Codex loads it when a task matches its description.
Can I use Docker Project Foundations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add docker/skills --skill docker-project-foundations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docker-project-foundations, .gemini/skills/docker-project-foundations, .github/skills/docker-project-foundations and .opencode/skills/docker-project-foundations in your project.
What does Docker Project Foundations need to run?
Going by SKILL.md and its folder, Docker Project Foundations needs a shell for the scripts in its folder and the command-line tools its instructions call (docker, bash, npm, brew and apt). Our summary lists: Node.js; A Bash shell; Docker. Compatibility (from SKILL.md): Requires Docker 20.10+ and Docker Compose v2..
Does Docker Project Foundations access the network?
SKILL.md contains no URLs. Its commands use docker and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Docker Project Foundations safe to install?
Our automated static check of SKILL.md flagged 3 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Docker Project Foundations use?
Docker Project Foundations is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docker Project Foundations use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 834 tokens, read only when the agent opens those files.
What are the alternatives to Docker Project Foundations?
Skills that share tags, products or a category with Docker Project Foundations: Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars), Os Eco Dep Sync (jayminwest/warren, 473 stars), Ddev (haxtheweb/haxcms-php, 130 stars) and Data Processing (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docker Project Foundations?
docker (a GitHub organization, an official publisher) maintains it in docker/skills, which has 539 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.
Source: docker/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
