跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 docker-project-foundations

Docker Project Foundations

在设置,初始化,或多克化项目时使用此技能,即使用户没有明确提及多克,而是描述了对容器化本地开发的需要,增加了数据库或缓存依赖性,或者在没有主机级安装的情况下运行服务. 封面多克文件,作曲:.yaml,并用多克最佳做法创作.dockerignore.

1696 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在设置,初始化,或多克化项目时使用此技能,即使用户没有明确提及多克,而是描述了对容器化本地开发的需要,增加了数据库或缓存依赖性,或者在没有主机级安装的情况下运行服务. 封面多克文件,作曲:.yaml,并用多克最佳做法创作.dockerignore.

何时用

这个技能

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Docker Project Foundations、Overview、When to use this skill、Do not use this skill when、Core guidance、Always create these three files。

文件分析

文件分析:除 SKILL.md 外,正文引用了 assets/dockerignore-example、assets/Dockerfile.simple、assets/compose-dev.yaml、references/project-structure.md、scripts/verify-setup.sh,属于带资源的技能包,这些文件按需再读。

官方 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.

Docker Project FoundationsOverviewWhen to use this skillDo not use this skill whenCore guidanceAlways create these three filesnpm registry credentialsPrefer Dockerized dependencies over host installsBootstrap checklistDevelopment vs productionFile placementRelated skills

兼容:Requires Docker 20.10+ and Docker Compose v2. · 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
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.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 5
  • assets/dockerignore-example
  • assets/Dockerfile.simple
  • assets/compose-dev.yaml
  • references/project-structure.md
  • scripts/verify-setup.sh

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「docker-project-foundations」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-7f1076235f92a2c0-Docker%E9%A1%B9%E7%9B%AE%E5%9F%BA%E9%87%91%E4%BC%9A.html
请存为 .cursor/skills/docker-project-foundations/SKILL.md 或 .claude/skills/docker-project-foundations/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/docker/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/docker/skills' --list

npx skills add 'https://github.com/docker/skills' --skill 'docker-project-foundations'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- 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. license: Apache-2.0 compatibility: Requires Docker 20.10+ and Docker Compose v2. --- # 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: 1. **`.dockerignore`** — Create this first so the initial build context is small and safe. See `assets/dockerignore-example` for a reference. 2. **`Dockerfile`** — Create a working starter image definition that the project can build and run with. See `assets/Dockerfile.simple`. 3. **`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 DOCKER_BUILDKIT=1 docker build --secret id=npmrc,src="$HOME/.npmrc" . ``` 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. ### 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 bash "/scripts/verify-setup.sh" [--help] ``` Replace `` 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 Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…