tech-docker
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when writing or modifying Dockerfiles or docker-compose.yml.
- Reads credentials
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When containerizing applications, optimize for image size, build speed, and security:
- Distinctive: line 13
Multi-Stage Builds: Always use multi-stage builds for compiled languages or build steps (like Node/React) to keep the final production …
- Very specific: line 14
Base Images: Use minimal base images (e.g., alpine, slim, or distroless) unless specific system dependencies are required.
- Very specific: line 16
Security: Never run the application as the root user.
- Very specific: line 17
Secrets: Never bake secrets or .env files into the image.
≈ “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.
Files
Docker Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When containerizing applications, optimize for image size, build speed, and security:
- Multi-Stage Builds: Always use multi-stage builds for compiled languages or build steps (like Node/React) to keep the final production image small.
- Base Images: Use minimal base images (e.g.,
alpine,slim, ordistroless) unless specific system dependencies are required. - Layer Caching: Order
Dockerfileinstructions from least frequently changed to most frequently changed. Copy package files (package.json,requirements.txt) and install dependencies before copying the source code. - Security: Never run the application as the
rootuser. Explicitly create and switch to a non-rootUSER. - Secrets: Never bake secrets or
.envfiles into the image. Use environment variables at runtime or Docker Secrets.
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
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.