Docker Best Practices

This one walks you through modern Docker practices with a clear bias toward security and minimal images. You get specific Dockerfile templates for multi-stage builds, the current base image hierarchy (Wolfi/Chainguard over Alpine over distroless), and layer ordering that actually makes sense for caching. It covers the usual production checklist: non-root users, health checks, resource limits, proper logging configs. The .dockerignore template alone will save you from shipping node_modules to production again. Best when you're moving past "it works on my machine" and need containers that won't embarrass you in production. Leans practical over theoretical.

skills.sh installs: 944
GitHub stars: 61
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add josiahsiegel/claude-plugin-marketplace --skill docker-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

🚨 CRITICAL GUIDELINES

Windows File Path Requirements

MANDATORY: Always Use Backslashes on Windows for File Paths

When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).

Examples:

❌ WRONG: D:/repos/project/file.tsx
✅ CORRECT: D:\repos\project\file.tsx

This applies to:

Edit tool file_path parameter
Write tool file_path parameter
All file operations on Windows systems

Documentation Guidelines

NEVER create new documentation files unless explicitly requested by the user.

Priority: Update existing README.md files rather than creating new documentation
Repository cleanliness: Keep repository root clean - only README.md unless user requests otherwise
Style: Documentation should be concise, direct, and professional - avoid AI-generated tone
User preference: Only create additional .md files when user specifically asks for documentation