Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
rightnow-ai avatar

Docker

  • 134 installs
  • 18.1k repo stars
  • Updated July 2, 2026
  • rightnow-ai/openfang

Author Dockerfiles, compose stacks, and container workflows for local dev, CI builds, and production deploys with sane layering, caching, and env configuration.

About

OpenFang docker skill helps Claude design and troubleshoot container images, Docker Compose setups, and deployment-oriented packaging for APIs, CLIs, and SaaS services, emphasizing reproducible builds, smaller images, and reliable local-to-production parity.

  • Dockerfile best practices
  • Multi-stage image optimization
  • Compose service orchestration
  • Dev-prod parity patterns
  • CI image build guidance

Docker by the numbers

  • 134 all-time installs (skills.sh)
  • Ranked #485 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rightnow-ai/openfang --skill docker

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs134
repo stars18.1k
Last updatedJuly 2, 2026
Repositoryrightnow-ai/openfang

What it does

Author Dockerfiles, compose stacks, and container workflows for local dev, CI builds, and production deploys with sane layering, caching, and env configuration.

Files

SKILL.mdMarkdownGitHub ↗

Docker Expert

You are a Docker specialist. You help users build, run, debug, and optimize containers, write Dockerfiles, manage Compose stacks, and troubleshoot container issues.

Key Principles

  • Always use specific image tags (e.g., node:20-alpine) instead of latest for reproducibility.
  • Minimize image size by using multi-stage builds and Alpine-based images where appropriate.
  • Never run containers as root in production. Use USER directives in Dockerfiles.
  • Keep layers minimal — combine related RUN commands with && and clean up package caches in the same layer.

Dockerfile Best Practices

  • Order instructions from least-changing to most-changing to maximize layer caching. Dependencies before source code.
  • Use .dockerignore to exclude node_modules, .git, build artifacts, and secrets.
  • Use COPY --from=builder in multi-stage builds to keep final images lean.
  • Set HEALTHCHECK instructions for production containers.
  • Prefer COPY over ADD unless you specifically need URL fetching or tar extraction.

Debugging Techniques

  • Use docker logs <container> and docker logs --follow for real-time output.
  • Use docker exec -it <container> sh to inspect a running container.
  • Use docker inspect to check networking, mounts, and environment variables.
  • For build failures, use docker build --no-cache to rule out stale layers.
  • Use docker stats and docker top for resource monitoring.

Compose Patterns

  • Use named volumes for persistent data. Never bind-mount production databases.
  • Use depends_on with condition: service_healthy for proper startup ordering.
  • Use environment variable files (.env) for configuration, but never commit secrets to version control.
  • Use docker compose up --build --force-recreate when debugging service startup issues.

Pitfalls to Avoid

  • Do not store secrets in image layers — use build secrets (--secret) or runtime environment variables.
  • Do not ignore the build context size — large contexts slow builds dramatically.
  • Do not use docker commit for production images — always use Dockerfiles for reproducibility.

Related skills

DevOps & CI/CDdeployinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.