From xonovex-skill-docker
Use when writing or editing Docker images and Compose files for production. Triggers on `Dockerfile`, `docker-compose.yml`, `.dockerignore`, and prompts about multi-stage builds, alpine/distroless base images, layer caching, non-root users, BuildKit, secrets, health checks, or image slimming, even when the user doesn't say 'Docker'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xonovex-skill-docker:docker-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Build optimization** - Multi-stage builds, small base images (alpine/distroless), see [references/multi-stage-builds.md](references/multi-stage-builds.md)
COPY/RUN — order layers from least-to-most-frequently-changed (deps before source)RUN apt-get install … && rm -rf /var/lib/apt/lists/* must be one layer — separate RUNs leave the apt cache in an earlier layer permanently.dockerignore is critical for build context size and to avoid leaking secrets — node_modules/ and .git/ aren't excluded by defaultCOPY --from=<stage> — forgetting it copies the whole heavy stage into the final imageENTRYPOINT + CMD interact: CMD provides default args to ENTRYPOINT; overriding CMD from docker run drops them, not appendsnpx claudepluginhub xonovex/platform --plugin xonovex-skill-dockerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.