[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EK2QB7WRWM9CEEW6D2X0MR":3,"skill-same:01M6EK2QB7WRWM9CEEW6D2X0MR":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6EK2QB7WRWM9CEEW6D2X0MR","docker-development",null,"Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: user wants to optimize a Dockerfile, create or improve docker-compose configurations, implement multi-stage builds, audit container security, reduce image size, or follow container best practices. Covers build performance, layer caching, secret management, and production-ready container patterns.","ArogyaReddy\u002Falirezarezvani-claude-skills","ArogyaReddy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12032101?v=4","01M6EJA7DAM8950XYAD875F4NY","01M6EJA7JSMD9SN617EJHTF2BQ",39,"MIT","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"docker","docker development","development","ready","agent skill","caching","docker-compose","container security","optimize","patterns","container development","compose","performance","image","improve","audit","create","security","dockerfile","orchestration","2026-11-10 10:12:30",false,"---\nname: \"docker-development\"\ndescription: \"Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: user wants to optimize a Dockerfile, create or improve docker-compose configurations, implement multi-stage builds, audit container security, reduce image size, or follow container best practices. Covers build performance, layer caching, secret management, and production-ready container patterns.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: engineering\n  updated: 2026-03-16\n---\n\n# Docker Development\n\n> Smaller images. Faster builds. Secure containers. No guesswork.\n\nOpinionated Docker workflow that turns bloated Dockerfiles into production-grade containers. Covers optimization, multi-stage builds, compose orchestration, and security hardening.\n\nNot a Docker tutorial — a set of concrete decisions about how to build containers that don't waste time, space, or attack surface.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Fdocker:optimize` | Analyze and optimize a Dockerfile for size, speed, and layer caching |\n| `\u002Fdocker:compose` | Generate or improve docker-compose.yml with best practices |\n| `\u002Fdocker:security` | Audit a Dockerfile or running container for security issues |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Optimize this Dockerfile\"\n- \"My Docker build is slow\"\n- \"Create a docker-compose for this project\"\n- \"Is this Dockerfile secure?\"\n- \"Reduce my Docker image size\"\n- \"Set up multi-stage builds\"\n- \"Docker best practices for [language\u002Fframework]\"\n- Any request involving: Dockerfile, docker-compose, container, image size, build cache, Docker security\n\nIf the user has a Dockerfile or wants to containerize something → this skill applies.\n\n---\n\n## Workflow\n\n### `\u002Fdocker:optimize` — Dockerfile Optimization\n\n1. **Analyze current state**\n   - Read the Dockerfile\n   - Identify base image and its size\n   - Count layers (each RUN\u002FCOPY\u002FADD = 1 layer)\n   - Check for common anti-patterns\n\n2. **Apply optimization checklist**\n\n   ```\n   BASE IMAGE\n   ├── Use specific tags, never :latest in production\n   ├── Prefer slim\u002Falpine variants (debian-slim > ubuntu > debian)\n   ├── Pin digest for reproducibility in CI: image@sha256:...\n   └── Match base to runtime needs (don't use python:3.12 for a compiled binary)\n\n   LAYER OPTIMIZATION\n   ├── Combine related RUN commands with && \\\n   ├── Order layers: least-changing first (deps before source code)\n   ├── Clean package manager cache in the same RUN layer\n   ├── Use .dockerignore to exclude unnecessary files\n   └── Separate build deps from runtime deps\n\n   BUILD CACHE\n   ├── COPY dependency files before source code (package.json, requirements.txt, go.mod)\n   ├── Install deps in a separate layer from code copy\n   ├── Use BuildKit cache mounts: --mount=type=cache,target=\u002Froot\u002F.cache\n   └── Avoid COPY . . before dependency installation\n\n   MULTI-STAGE BUILDS\n   ├── Stage 1: build (full SDK, build tools, dev deps)\n   ├── Stage 2: runtime (minimal base, only production artifacts)\n   ├── COPY --from=builder only what's needed\n   └── Final image should have NO build tools, NO source code, NO dev deps\n   ```\n\n3. **Generate optimized Dockerfile**\n   - Apply all relevant optimizations\n   - Add inline comments explaining each decision\n   - Report estimated size reduction\n\n4. **Validate**\n   ```bash\n   python3 scripts\u002Fdockerfile_analyzer.py Dockerfile\n   ```\n\n### `\u002Fdocker:compose` — Docker Compose Configuration\n\n1. **Identify services**\n   - Application (web, API, worker)\n   - Database (postgres, mysql, redis, mongo)\n   - Cache (redis, memcached)\n   - Queue (rabbitmq, kafka)\n   - Reverse proxy (nginx, traefik, caddy)\n\n2. **Apply compose best practices**\n\n   ```\n   SERVICES\n   ├── Use depends_on with condition: service_healthy\n   ├── Add healthchecks for every service\n   ├── Set resource limits (mem_limit, cpus)\n   ├── Use named volumes for persistent data\n   └── Pin image versions\n\n   NETWORKING\n   ├── Create explicit networks (don't rely on default)\n   ├── Separate frontend and backend networks\n   ├── Only expose ports that need external access\n   └── Use internal: true for backend-only networks\n\n   ENVIRONMENT\n   ├── Use env_file for secrets, not inline environment\n   ├── Never commit .env files (add to .gitignore)\n   ├── Use variable substitution: ${VAR:-default}\n   └── Document all required env vars\n\n   DEVELOPMENT vs PRODUCTION\n   ├── Use compose profiles or override files\n   ├── Dev: bind mounts for hot reload, debug ports exposed\n   ├── Prod: named volumes, no debug ports, restart: unless-stopped\n   └── docker-compose.override.yml for dev-only config\n   ```\n\n3. **Generate compose file**\n   - Output docker-compose.yml with healthchecks, networks, volumes\n   - Generate .env.example with all required variables documented\n   - Add dev\u002Fprod profile annotations\n\n### `\u002Fdocker:security` — Container Security Audit\n\n1. **Dockerfile audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Running as root | Critical | Add `USER nonroot` after creating user |\n   | Using :latest tag | High | Pin to specific version |\n   | Secrets in ENV\u002FARG | Critical | Use BuildKit secrets: `--mount=type=secret` |\n   | COPY with broad glob | Medium | Use specific paths, add .dockerignore |\n   | Unnecessary EXPOSE | Low | Only expose ports the app uses |\n   | No HEALTHCHECK | Medium | Add HEALTHCHECK with appropriate interval |\n   | Privileged instructions | High | Avoid `--privileged`, drop capabilities |\n   | Package manager cache retained | Low | Clean in same RUN layer |\n\n2. **Runtime security checks**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Container running as root | Critical | Set user in Dockerfile or compose |\n   | Writable root filesystem | Medium | Use `read_only: true` in compose |\n   | All capabilities retained | High | Drop all, add only needed: `cap_drop: [ALL]` |\n   | No resource limits | Medium | Set `mem_limit` and `cpus` |\n   | Host network mode | High | Use bridge or custom network |\n   | Sensitive mounts | Critical | Never mount \u002Fetc, \u002Fvar\u002Frun\u002Fdocker.sock in prod |\n   | No log driver configured | Low | Set `logging:` with size limits |\n\n3. **Generate security report**\n   ```\n   SECURITY AUDIT — [Dockerfile\u002FImage name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with fix recommendations]\n   ```\n\n---\n\n## Tooling\n\n### `scripts\u002Fdockerfile_analyzer.py`\n\nCLI utility for static analysis of Dockerfiles.\n\n**Features:**\n- Layer count and optimization suggestions\n- Base image analysis with size estimates\n- Anti-pattern detection (15+ rules)\n- Security issue flagging\n- Multi-stage build detection and validation\n- JSON and text output\n\n**Usage:**\n```bash\n# Analyze a Dockerfile\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile\n\n# JSON output\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile --output json\n\n# Analyze with security focus\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile --security\n\n# Check a specific directory\npython3 scripts\u002Fdockerfile_analyzer.py path\u002Fto\u002FDockerfile\n```\n\n### `scripts\u002Fcompose_validator.py`\n\nCLI utility for validating docker-compose files.\n\n**Features:**\n- Service dependency validation\n- Healthcheck presence detection\n- Network configuration analysis\n- Volume mount validation\n- Environment variable audit\n- Port conflict detection\n- Best practice scoring\n\n**Usage:**\n```bash\n# Validate a compose file\npython3 scripts\u002Fcompose_validator.py docker-compose.yml\n\n# JSON output\npython3 scripts\u002Fcompose_validator.py docker-compose.yml --output json\n\n# Strict mode (fail on warnings)\npython3 scripts\u002Fcompose_validator.py docker-compose.yml --strict\n```\n\n---\n\n## Multi-Stage Build Patterns\n\n### Pattern 1: Compiled Language (Go, Rust, C++)\n\n```dockerfile\n# Build stage\nFROM golang:1.22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 go build -ldflags=\"-s -w\" -o \u002Fapp\u002Fserver .\u002Fcmd\u002Fserver\n\n# Runtime stage\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12\nCOPY --from=builder \u002Fapp\u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Pattern 2: Node.js \u002F TypeScript\n\n```dockerfile\n# Dependencies stage\nFROM node:20-alpine AS deps\nWORKDIR \u002Fapp\nCOPY package.json package-lock.json .\u002F\nRUN npm ci --production=false\n\n# Build stage\nFROM deps AS builder\nCOPY . .\nRUN npm run build\n\n# Runtime stage\nFROM node:20-alpine\nWORKDIR \u002Fapp\nRUN addgroup -g 1001 -S appgroup && adduser -S appuser -u 1001\nCOPY --from=builder \u002Fapp\u002Fdist .\u002Fdist\nCOPY --from=deps \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY package.json .\u002F\nUSER appuser\nEXPOSE 3000\nCMD [\"node\", \"dist\u002Findex.js\"]\n```\n\n### Pattern 3: Python\n\n```dockerfile\n# Build stage\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --prefix=\u002Finstall -r requirements.txt\n\n# Runtime stage\nFROM python:3.12-slim\nWORKDIR \u002Fapp\nRUN groupadd -r appgroup && useradd -r -g appgroup appuser\nCOPY --from=builder \u002Finstall \u002Fusr\u002Flocal\nCOPY . .\nUSER appuser\nEXPOSE 8000\nCMD [\"python\", \"-m\", \"uvicorn\", \"main:app\", \"--host\", \"0.0.0.0\", \"--port\", \"8000\"]\n```\n\n---\n\n## Base Image Decision Tree\n\n```\nIs it a compiled binary (Go, Rust, C)?\n├── Yes → distroless\u002Fstatic or scratch\n└── No\n    ├── Need a shell for debugging?\n    │   ├── Yes → alpine variant (e.g., node:20-alpine)\n    │   └── No → distroless variant\n    ├── Need glibc (not musl)?\n    │   ├── Yes → slim variant (e.g., python:3.12-slim)\n    │   └── No → alpine variant\n    └── Need specific OS packages?\n        ├── Many → debian-slim\n        └── Few → alpine + apk add\n```\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **Dockerfile uses :latest** → Suggest pinning to a specific version tag.\n- **No .dockerignore** → Create one. At minimum: `.git`, `node_modules`, `__pycache__`, `.env`.\n- **COPY . . before dependency install** → Cache bust. Reorder to install deps first.\n- **Running as root** → Add USER instruction. No exceptions for production.\n- **Secrets in ENV or ARG** → Use BuildKit secret mounts. Never bake secrets into layers.\n- **Image over 1GB** → Multi-stage build required. No reason for a production image this large.\n- **No healthcheck** → Add one. Orchestrators (Compose, K8s) need it for proper lifecycle management.\n- **apt-get without cleanup in same layer** → `rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*` in the same RUN.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills.git\ncp -r claude-skills\u002Fengineering\u002Fdocker-development ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill docker-development --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-docker-development\n```\n\n---\n\n## Related Skills\n\n- **senior-devops** — Broader DevOps scope (CI\u002FCD, IaC, monitoring). Complementary — use docker-development for container-specific work, senior-devops for pipeline and infrastructure.\n- **senior-security** — Application security. Complementary — docker-development covers container security, senior-security covers application-level threats.\n- **autoresearch-agent** — Can optimize Docker build times or image sizes as measurable experiments.\n- **ci-cd-pipeline-builder** — Pipeline construction. Complementary — docker-development builds the containers, ci-cd-pipeline-builder deploys them.\n","# Docker Development\n\n> Smaller images. Faster builds. Secure containers. No guesswork.\n\nOpinionated Docker workflow that turns bloated Dockerfiles into production-grade containers. Covers optimization, multi-stage builds, compose orchestration, and security hardening.\n\nNot a Docker tutorial — a set of concrete decisions about how to build containers that don't waste time, space, or attack surface.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Fdocker:optimize` | Analyze and optimize a Dockerfile for size, speed, and layer caching |\n| `\u002Fdocker:compose` | Generate or improve docker-compose.yml with best practices |\n| `\u002Fdocker:security` | Audit a Dockerfile or running container for security issues |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Optimize this Dockerfile\"\n- \"My Docker build is slow\"\n- \"Create a docker-compose for this project\"\n- \"Is this Dockerfile secure?\"\n- \"Reduce my Docker image size\"\n- \"Set up multi-stage builds\"\n- \"Docker best practices for [language\u002Fframework]\"\n- Any request involving: Dockerfile, docker-compose, container, image size, build cache, Docker security\n\nIf the user has a Dockerfile or wants to containerize something → this skill applies.\n\n---\n\n## Workflow\n\n### `\u002Fdocker:optimize` — Dockerfile Optimization\n\n1. **Analyze current state**\n   - Read the Dockerfile\n   - Identify base image and its size\n   - Count layers (each RUN\u002FCOPY\u002FADD = 1 layer)\n   - Check for common anti-patterns\n\n2. **Apply optimization checklist**\n\n   ```\n   BASE IMAGE\n   ├── Use specific tags, never :latest in production\n   ├── Prefer slim\u002Falpine variants (debian-slim > ubuntu > debian)\n   ├── Pin digest for reproducibility in CI: image@sha256:...\n   └── Match base to runtime needs (don't use python:3.12 for a compiled binary)\n\n   LAYER OPTIMIZATION\n   ├── Combine related RUN commands with && \\\n   ├── Order layers: least-changing first (deps before source code)\n   ├── Clean package manager cache in the same RUN layer\n   ├── Use .dockerignore to exclude unnecessary files\n   └── Separate build deps from runtime deps\n\n   BUILD CACHE\n   ├── COPY dependency files before source code (package.json, requirements.txt, go.mod)\n   ├── Install deps in a separate layer from code copy\n   ├── Use BuildKit cache mounts: --mount=type=cache,target=\u002Froot\u002F.cache\n   └── Avoid COPY . . before dependency installation\n\n   MULTI-STAGE BUILDS\n   ├── Stage 1: build (full SDK, build tools, dev deps)\n   ├── Stage 2: runtime (minimal base, only production artifacts)\n   ├── COPY --from=builder only what's needed\n   └── Final image should have NO build tools, NO source code, NO dev deps\n   ```\n\n3. **Generate optimized Dockerfile**\n   - Apply all relevant optimizations\n   - Add inline comments explaining each decision\n   - Report estimated size reduction\n\n4. **Validate**\n   ```bash\n   python3 scripts\u002Fdockerfile_analyzer.py Dockerfile\n   ```\n\n### `\u002Fdocker:compose` — Docker Compose Configuration\n\n1. **Identify services**\n   - Application (web, API, worker)\n   - Database (postgres, mysql, redis, mongo)\n   - Cache (redis, memcached)\n   - Queue (rabbitmq, kafka)\n   - Reverse proxy (nginx, traefik, caddy)\n\n2. **Apply compose best practices**\n\n   ```\n   SERVICES\n   ├── Use depends_on with condition: service_healthy\n   ├── Add healthchecks for every service\n   ├── Set resource limits (mem_limit, cpus)\n   ├── Use named volumes for persistent data\n   └── Pin image versions\n\n   NETWORKING\n   ├── Create explicit networks (don't rely on default)\n   ├── Separate frontend and backend networks\n   ├── Only expose ports that need external access\n   └── Use internal: true for backend-only networks\n\n   ENVIRONMENT\n   ├── Use env_file for secrets, not inline environment\n   ├── Never commit .env files (add to .gitignore)\n   ├── Use variable substitution: ${VAR:-default}\n   └── Document all required env vars\n\n   DEVELOPMENT vs PRODUCTION\n   ├── Use compose profiles or override files\n   ├── Dev: bind mounts for hot reload, debug ports exposed\n   ├── Prod: named volumes, no debug ports, restart: unless-stopped\n   └── docker-compose.override.yml for dev-only config\n   ```\n\n3. **Generate compose file**\n   - Output docker-compose.yml with healthchecks, networks, volumes\n   - Generate .env.example with all required variables documented\n   - Add dev\u002Fprod profile annotations\n\n### `\u002Fdocker:security` — Container Security Audit\n\n1. **Dockerfile audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Running as root | Critical | Add `USER nonroot` after creating user |\n   | Using :latest tag | High | Pin to specific version |\n   | Secrets in ENV\u002FARG | Critical | Use BuildKit secrets: `--mount=type=secret` |\n   | COPY with broad glob | Medium | Use specific paths, add .dockerignore |\n   | Unnecessary EXPOSE | Low | Only expose ports the app uses |\n   | No HEALTHCHECK | Medium | Add HEALTHCHECK with appropriate interval |\n   | Privileged instructions | High | Avoid `--privileged`, drop capabilities |\n   | Package manager cache retained | Low | Clean in same RUN layer |\n\n2. **Runtime security checks**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Container running as root | Critical | Set user in Dockerfile or compose |\n   | Writable root filesystem | Medium | Use `read_only: true` in compose |\n   | All capabilities retained | High | Drop all, add only needed: `cap_drop: [ALL]` |\n   | No resource limits | Medium | Set `mem_limit` and `cpus` |\n   | Host network mode | High | Use bridge or custom network |\n   | Sensitive mounts | Critical | Never mount \u002Fetc, \u002Fvar\u002Frun\u002Fdocker.sock in prod |\n   | No log driver configured | Low | Set `logging:` with size limits |\n\n3. **Generate security report**\n   ```\n   SECURITY AUDIT — [Dockerfile\u002FImage name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with fix recommendations]\n   ```\n\n---\n\n## Tooling\n\n### `scripts\u002Fdockerfile_analyzer.py`\n\nCLI utility for static analysis of Dockerfiles.\n\n**Features:**\n- Layer count and optimization suggestions\n- Base image analysis with size estimates\n- Anti-pattern detection (15+ rules)\n- Security issue flagging\n- Multi-stage build detection and validation\n- JSON and text output\n\n**Usage:**\n```bash\n# Analyze a Dockerfile\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile\n\n# JSON output\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile --output json\n\n# Analyze with security focus\npython3 scripts\u002Fdockerfile_analyzer.py Dockerfile --security\n\n# Check a specific directory\npython3 scripts\u002Fdockerfile_analyzer.py path\u002Fto\u002FDockerfile\n```\n\n### `scripts\u002Fcompose_validator.py`\n\nCLI utility for validating docker-compose files.\n\n**Features:**\n- Service dependency validation\n- Healthcheck presence detection\n- Network configuration analysis\n- Volume mount validation\n- Environment variable audit\n- Port conflict detection\n- Best practice scoring\n\n**Usage:**\n```bash\n# Validate a compose file\npython3 scripts\u002Fcompose_validator.py docker-compose.yml\n\n# JSON output\npython3 scripts\u002Fcompose_validator.py docker-compose.yml --output json\n\n# Strict mode (fail on warnings)\npython3 scripts\u002Fcompose_validator.py docker-compose.yml --strict\n```\n\n---\n\n## Multi-Stage Build Patterns\n\n### Pattern 1: Compiled Language (Go, Rust, C++)\n\n```dockerfile\n# Build stage\nFROM golang:1.22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 go build -ldflags=\"-s -w\" -o \u002Fapp\u002Fserver .\u002Fcmd\u002Fserver\n\n# Runtime stage\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12\nCOPY --from=builder \u002Fapp\u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Pattern 2: Node.js \u002F TypeScript\n\n```dockerfile\n# Dependencies stage\nFROM node:20-alpine AS deps\nWORKDIR \u002Fapp\nCOPY package.json package-lock.json .\u002F\nRUN npm ci --production=false\n\n# Build stage\nFROM deps AS builder\nCOPY . .\nRUN npm run build\n\n# Runtime stage\nFROM node:20-alpine\nWORKDIR \u002Fapp\nRUN addgroup -g 1001 -S appgroup && adduser -S appuser -u 1001\nCOPY --from=builder \u002Fapp\u002Fdist .\u002Fdist\nCOPY --from=deps \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY package.json .\u002F\nUSER appuser\nEXPOSE 3000\nCMD [\"node\", \"dist\u002Findex.js\"]\n```\n\n### Pattern 3: Python\n\n```dockerfile\n# Build stage\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --prefix=\u002Finstall -r requirements.txt\n\n# Runtime stage\nFROM python:3.12-slim\nWORKDIR \u002Fapp\nRUN groupadd -r appgroup && useradd -r -g appgroup appuser\nCOPY --from=builder \u002Finstall \u002Fusr\u002Flocal\nCOPY . .\nUSER appuser\nEXPOSE 8000\nCMD [\"python\", \"-m\", \"uvicorn\", \"main:app\", \"--host\", \"0.0.0.0\", \"--port\", \"8000\"]\n```\n\n---\n\n## Base Image Decision Tree\n\n```\nIs it a compiled binary (Go, Rust, C)?\n├── Yes → distroless\u002Fstatic or scratch\n└── No\n    ├── Need a shell for debugging?\n    │   ├── Yes → alpine variant (e.g., node:20-alpine)\n    │   └── No → distroless variant\n    ├── Need glibc (not musl)?\n    │   ├── Yes → slim variant (e.g., python:3.12-slim)\n    │   └── No → alpine variant\n    └── Need specific OS packages?\n        ├── Many → debian-slim\n        └── Few → alpine + apk add\n```\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **Dockerfile uses :latest** → Suggest pinning to a specific version tag.\n- **No .dockerignore** → Create one. At minimum: `.git`, `node_modules`, `__pycache__`, `.env`.\n- **COPY . . before dependency install** → Cache bust. Reorder to install deps first.\n- **Running as root** → Add USER instruction. No exceptions for production.\n- **Secrets in ENV or ARG** → Use BuildKit secret mounts. Never bake secrets into layers.\n- **Image over 1GB** → Multi-stage build required. No reason for a production image this large.\n- **No healthcheck** → Add one. Orchestrators (Compose, K8s) need it for proper lifecycle management.\n- **apt-get without cleanup in same layer** → `rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*` in the same RUN.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills.git\ncp -r claude-skills\u002Fengineering\u002Fdocker-development ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill docker-development --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-docker-development\n```\n\n---\n\n## Related Skills\n\n- **senior-devops** — Broader DevOps scope (CI\u002FCD, IaC, monitoring). Complementary — use docker-development for container-specific work, senior-devops for pipeline and infrastructure.\n- **senior-security** — Application security. Complementary — docker-development covers container security, senior-security covers application-level threats.\n- **autoresearch-agent** — Can optimize Docker build times or image sizes as measurable experiments.\n- **ci-cd-pipeline-builder** — Pipeline construction. Complementary — docker-development builds the containers, ci-cd-pipeline-builder deploys them.\n",{"name":5,"license":14,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":58},"Alireza Rezvani",1773619200000,"1.0.0","engineering","main","dc799ac68cfdc454fc55edaf3f054651f645f738","engineering\u002Fdocker-development",10,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills","https:\u002F\u002Fgithub.com\u002FArogyaReddy","2026-03-18 00:40:19",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill docker-development",{"tool":72,"command":73},"bunx","bunx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill docker-development",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill docker-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002FSKILL.md",true,[80,86,90,94,100],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",629,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002F.claude-plugin\u002Fplugin.json",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcompose-patterns.md",5877,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002Freferences\u002Fcompose-patterns.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdockerfile-best-practices.md",5243,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002Freferences\u002Fdockerfile-best-practices.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fcompose_validator.py","SCRIPT","脚本",13506,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002Fscripts\u002Fcompose_validator.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fdockerfile_analyzer.py",13870,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fdocker-development\u002Fscripts\u002Fdockerfile_analyzer.py",[105,132,158,187,206,230],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":49},"01M6EKFK0DB8WVYWCN59CM5SEQ","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","use","risk matrix","Market","control","iso","medical","iso 14971","identification","post",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":49},"01M6EKFDZ7KES3X3HH8KBHR9JF","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[139,140,141,142,143,144,145,146,147,148,149,150,151,152,128,153,154,155,156,157],"regulatory affairs head","regulatory","head","documentation","documents","packages","plan","access","write","evidence","standards","intelligence","across","strategies","clinical","pathway","de","respond","medical devices",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":172,"publishedAt":49},"01M6EKF980P5MQBEQQAKB2JE6V","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[164,167],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":168,"categoryName":169,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[173,174,175,176,177,178,142,44,179,180,181,123,182,183,184,126,127,128,185,186],"quality manager qms iso13485","quality","design","review","support","workflows","actions","compliance","system","up","maintenance","document","records","ISO 13485",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":196,"publishedAt":49},"01M6EKF4ZN8ZJJP3K6FM1WEM85","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[193],{"categoryNo":194,"categoryName":195,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000037","律师与法务",[197,174,176,198,41,199,200,180,201,181,114,202,140,203,204,205,127,186],"quality manager qmr","policy","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":49},"01M6EKF15YKH2AQB45MH4Y6S08","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":194,"categoryName":195,"taxonomyType":170,"taxonomyTypeDesc":171},[142,217,174,176,218,219,44,121,220,181,221,222,223,224,225,128,226,227,228,229],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":236,"publishedAt":49},"01M6EKEXQMCQC11A5WR9GEPC4S","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[44,237,238,239,240,241,242,243,114,123,244,245,127,128,186],"qms audit expert","expert","planning","verification","execution","classification","schedule","checklist","device"]