docker-expert

Designs and reviews Dockerfiles and Compose setups for on-prem monorepo deployments.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill docker-expert-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-expert
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/docker-expert
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill docker-expert-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Containerizing a pnpm monorepo for on-prem MVP deployment often leads to bloated images, root-privileged containers, leaked secrets, and over-engineered orchestration. This Skill provides concrete rules, patterns, and review checklists to build secure, reproducible Docker setups aligned with the project's actual baseline. ## Core Features & Use Cases - Dockerfile Design & Review: Multi-stage builds, selective layer copying for cache efficiency, non-root runtimes, and healthchecks tailored to pnpm monorepo services. - Compose & Service Orchestration: Simple networks, explicit service dependencies, startup ordering, and per-environment configuration for local and on-prem MVP deployments. - Image Hardening: Keeps secrets out of images and versioned code, minimizes runtime attack surface, and flags anti-patterns like early COPY . . or credentials in Compose files. - Use Case: You need a production Dockerfile for a backend service in the monorepo. The Skill guides a multi-stage build that caches pnpm dependencies, ships only runtime artifacts, runs as a non-root user, and includes a healthcheck. ## Quick Start Ask the assistant to review or write a Dockerfile and Compose setup for a monorepo service following the on-prem security baseline.

Frequently Asked Questions about docker-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Dockerfile for a pnpm monorepo service?

Use a multi-stage build that copies only the manifests and files needed for dependency installation first, leveraging Docker layer caching. Separate dependency install, build, and runtime stages so the final image contains only the artifacts the service needs.

How to reduce Docker image size for Node.js backends?

Apply multi-stage builds so build toolchains stay out of the runtime image, and copy only production artifacts into the final stage. Avoid early `COPY . .` statements that invalidate cache and pull unnecessary files into the image.

Should containers run as root in production?

No, containers should run as a non-root user whenever viable to limit the impact of a compromise. The Skill's hardening rules require minimal runtime privileges, secrets kept out of images, and no unnecessary debug tools in production images.

Does this approach support Kubernetes deployments?

No, the baseline is deliberately Docker on-prem for MVP deployment without Kubernetes or cloud orchestration. Proposals that push toward another operational model require an explicit documented decision and escalation.

Why do Docker builds get slow in a monorepo?

Builds slow down when Dockerfiles copy the entire repo early, busting the cache on every change. Copy dependency manifests first, install with pnpm, then copy source code so unchanged dependencies stay cached.