agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/containerize/SKILL.md

containerize

Skill1 starsChanged 41 days agoMITView on GitHub

Package apps with Docker and Compose sanely. Use when adding containers, fixing Docker builds, or setting up local service stacks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write Dockerfile to reproduce that path.

    line 19
  2. Distinctive:

    Add Compose services for dependent DBs/caches as needed.

    line 20
  3. Distinctive:

    Verify: build → run → hit health endpoint/smoke command.

    line 22
  4. Distinctive:

    Prefer official base images from trusted registries.

    line 27
  5. Distinctive:

    Keep local Compose convenient without pretending to be full prod orchestration.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Containerize

Defaults

  • Small base images; pin tags/digests when reproducibility matters
  • Non-root user when feasible
  • Multi-stage builds for compiled/static assets
  • .dockerignore excludes secrets, .git, and heavy unused trees
  • One process per container; Compose for dependencies

Process

  1. Detect how the app builds/runs locally.
  2. Write Dockerfile to reproduce that path.
  3. Add Compose services for dependent DBs/caches as needed.
  4. Pass config via env; never bake secrets into layers.
  5. Verify: build → run → hit health endpoint/smoke command.

Rules

  • Match production runtime version closely enough to catch issues.
  • Prefer official base images from trusted registries.
  • Keep local Compose convenient without pretending to be full prod orchestration.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free