Dockerfile
A universal collection of reusable Loop Engineering kits for AI coding agents—not just prompts. Each kit combines Skills, Rules, Templates, workflows, and validation loops to help agents autonomously plan, execute, verify, fix, and improve engineering tasks.
npx -y skills add KhaiTrang1995/agentic-awesome-kits --skill dockerfileAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
- 7 stars7 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
Generate an optimized Dockerfile — multi-stage build, security hardening, small image size.
SKILL.md
1.2 KB, 275 tokens by cl100k_base, as published. Nobody here has run it
/dockerfile — Generate a Dockerfile
Input examples
/dockerfile .NET 10 Minimal API --prod
/dockerfile Angular 20 nginx --prod
/dockerfile Python FastAPI
/dockerfile Go service --prod
/dockerfile --dev fullstack .NET + Angular (docker-compose dev)
Process
- Detect the stack → pick the right base image
- Multi-stage build: build stage → runtime stage
- Security hardening
- L1 approval → Write
Mandatory rules
- Multi-stage build — separate build and runtime
- Non-root user — NEVER run the container as root
- Specific tag —
mcr.microsoft.com/dotnet/aspnet:10.0-alpine, NEVERlatest - COPY before RUN — leverage layer caching (copy csproj/package.json first, restore, then copy source)
- .dockerignore — exclude bin/, obj/, node_modules/, .git/
- HEALTHCHECK — mandatory for production
- NEVER hardcode secrets/connection strings — use env vars
- Alpine-based whenever possible (small image size)
Output
Dockerfile
.dockerignore
References
- @.claude/rules/docker-conventions.md
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 3 of the 12 instructions most security skills give in 275 tokens
Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07
- Parameterize all database queriesin 68 of 648, across 51 files
- Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
- Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
- Configure security headersin 35 of 648, across 19 files
- Validate all inputsin 32 of 648, across 24 files
- Validate all external input at the system boundaryin 29 of 648, across 19 files
- Run containers as a non-root userhere, and in 28 of 648, across 15 files
- Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
- Run dependency audits before every releasein 21 of 648, across 10 files
- Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
- Copy dependencies before source codehere, and in 20 of 648, across 9 files
- Store secrets in environment variableshere, and in 20 of 648, across 18 files
Said here and by no other author read
- pick the correct base image for the detected stack
- separate the build stage and runtime stage
- use specific image tags instead of latest
- add a healthcheck for production builds
- prefer alpine-based images to minimize size
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.