agentsclimarketplace

10x docker

Skill arhuman/claude-plugins/plugins/10x/skills/10x-docker

Install
npx -y skills add arhuman/claude-plugins --skill 10x-docker

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Docker and docker-compose best practices. Use for any Docker task: Dockerfiles (multi-stage builds, alpine, non-root), docker compose services (Go API, frontend, MariaDB, Oracle), healthchecks, volumes, networks, and K8S-compatible configurations.

SKILL.md

3.9 KB, 894 tokens by cl100k_base, as published. Nobody here has run it

10x Docker

Dockerfile

For Go API please follow the recommendations in ./references/go-api-dockerfile.md For Frontend applications follow the recommendations in ./references/frontend-dockerfile.md

Dockerfile Performance

  1. Layer Caching:

    • Copy dependency files first (go.mod, package.json)
    • Run dependency download before copying source
    • Order COPY commands from least to most frequently changed

  2. Build Optimization:

    • Use multi-stage builds
    • Minimize number of layers
    • Combine RUN commands where appropriate

  3. Development Speed:

    • Provide Dockerfile_localbuild for fast iteration
    • Use volume mounts for live reload
    • Implement proper healthchecks

Docker-compose.yml

  • Omit version field (recommended) or use version: '3.9'
  • Use services: as top-level key

Standard Service Patterns

For MariaDB service read ./references/mariadb-docker-compose-service.md For Oracle service read ./references/oracle-docker-compose-service.md For Go API service read ./references/go-api-docker-compose-service.md For Frontend service read ./references/frontend-docker-compose-service.md

Verification and Troubleshooting

Before completing any task, run through ./references/verification-checklist.md. For build/runtime/permission issues, consult ./references/troubleshooting.md.

Volumes

Common Volume Patterns:

  1. Init Scripts: ./conf/docker/initdb:/docker-entrypoint-initdb.d
  2. Configuration: ./conf/docker/mariadb.cnf:/etc/mysql/mariadb.cnf
  3. Environment: ./env.sample:/home/dinfo/conf/.env
  4. Logs: /tmp/logs:/tmp/logs
  5. Runtime Config: ./conf/docker/environment.json:/usr/share/nginx/html/assets/environments/environment.json

Ports

Standard Port Mappings:

  • Application APIs: 8080:8080
  • MariaDB: 23306:3306 (non-conflicting external port)
  • Oracle: 1521:1521, 5500:5500
  • PostgreSQL: 25432:5432

Networks

  • Use default network for simple setups
  • Explicit networks only when needed for isolation

Environment Variables

Naming Convention:

  • UPPERCASE with underscores
  • Prefixed with component name (e.g., MARIADB_, ORACLE_)
  • Use .env files for sensitive data (not committed)
  • Use env.sample as template

Common Variables:

  • MARIADB_ROOT_PASSWORD, MARIADB_DATABASE, MARIADB_USER, MARIADB_PASSWORD
  • TZ=Europe/Zurich
  • DOCKERFILE for build variant selection

Best Practices

Security

  1. Non-root User:

    • Always run as non-root (USER 1001)
    • Create dedicated user/group
    • Set proper permissions for K8S compatibility

  2. Minimal Images:

    • Use alpine or slim variants when possible
    • Multi-stage builds to reduce final image size

  3. Secrets Management:

    • Never commit passwords in docker-compose.yml
    • Use environment variables
    • Provide env.sample templates
    • Use Docker secrets for production

Maintainability

  1. Naming:

    • Container names: project-component (e.g., persons-api, persons-db)
    • Image names: match container names
    • Image tag: use explicit version number instead of 'latest'
    • Service names: descriptive and consistent

  2. Documentation:

    • Comment architecture-specific choices
    • Document environment variables
    • Provide usage examples in README

  3. Variants:

    • Dockerfile - Production with multi-stage build
    • Dockerfile_localbuild - Local development (pre-built binary)
    • Dockerfile_test - Testing environment
    • docker-compose.yml - Main composition
    • docker-compose.override.yml - Local overrides
    • docker-compose-test.yml - Test environment
    • docker-compose-prod.yml - Production settings

Gives 3 of the 12 instructions most containers cloud skills give in 894 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-06

  • run containers as a non-root userhere, and in 69 of 607, across 49 files
  • use multi-stage buildshere, and in 52 of 607, across 41 files
  • use Promise.all for independent operationsin 47 of 607, across 13 files
  • import directly instead of barrel filesin 46 of 607, across 12 files
  • use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • authenticate server actions like API routesin 35 of 607, across 7 files
  • use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • use React.cache for per-request deduplicationin 34 of 607, across 10 files
  • copy dependency files before source codehere, and in 34 of 607, across 21 files

Said here and by no other author read

  • name environment variables in uppercase with underscores
  • omit the compose version field or use 3.9
  • use default networks for simple setups
  • comment architecture-specific choices

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.