create
/create
Creates the Docker environment of a project that has none. Writes base, dev and prod compose files, a Dockerfile per service in docker/<domain>, dev hot reload, lean prod and docker/README.md. Use when asked to dockerize a project, or for compose, a Dockerfile or a dev or prod setup from scratch.
- Author
- kamoca-labs ↗
- Repository
- docker ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Creates the Docker environment of a project that has none. Writes base, dev and prod compose files, a Dockerfile per service in docker/<domain>, dev hot reload, lean prod and docker/README.md. Use when asked to dockerize a project, or for compose, a Dockerfile or a dev or prod setup from scratch.
Arguments
/create [dev|prod] [stack or services]
Original author description
Creates the Docker environment of a project that has none. Writes base, dev and prod compose files, a Dockerfile per service in docker/<domain>, dev hot reload, lean prod and docker/README.md. Use when asked to dockerize a project, or for compose, a Dockerfile or a dev or prod setup from scratch.
How it works
- Steps
- Out of scope
SKILL.md preview
---
name: create
description: Creates the Docker environment of a project that has none. Writes base, dev and prod compose files, a Dockerfile per service in docker/<domain>, dev hot reload, lean prod and docker/README.md. Use when asked to dockerize a project, or for compose, a Dockerfile or a dev or prod setup from scratch.
argument-hint: "[dev|prod] [stack or services]"
---
# docker:create
First make it **work**, already inside the rules. Optimize later with `docker:tune`. Without an argument, create dev and prod. With `dev`, create the base and dev.
The references are in `../docker/references/`. Read each one with the `Read` tool at the step where it applies. Read it only if the project needs it.
## Steps
1. **Survey the project.** Find the stack from the manifests and the lockfile. Find the dev command, the port and the services the code needs (database, cache, queue, e-mail). Decide if an HTTP server must sit in front (php-fpm always needs one. Static files, reverse proxy and HTTPS also need one). If Docker already exists, stop and use `docker:tune`.
2. **Rules and versions.** Read `../docker/references/rules.md` and `../docker/references/versions.md`. Look up the tag of each image on Docker Hub.
3. **Show the plan and wait for approval.** List the files, the services with the tag you found, the ports and the variables with their defaults. Use a short table.
4. **Base.** Write `compose.yaml` with what is equal in dev and prod. Write a `docker/<domain>/Dockerfile` with its `Dockerfile.dockerignore` for **every** service, including third-party services (`../docker/references/production.md` has the template). Name every service after its role (`backend`, `frontend`, `database`, `cache`, `proxy`). Use the technology name (`node`, `postgres`) only when the user asks for it. Add `container_name` and `healthcheck`. Add `depends_on` with `condition: service_healthy` only where the app needs the service to be up.
5. **Dev.** Read `../docker/references/development.md` and `../docker/references/hot-reload.md`. Write it in `compose.dev.yaml`.
6. **Prod.** Read `../docker/references/production.md`. Write it in `compose.prod.yaml`.
7. **HTTP server**, if there is one. Read `../docker/references/https.md`. Add the dev certificate and the prod simulation certificate.
8. **`.env`, `.gitignore` and folders.** Put the generated `UID` and `GID` in `./.env` and the secrets in `./.env.prod` (`openssl rand -hex 24`). In `.gitignore`, add the lines from `../docker/references/rules.md`. Create the folders `docker/<service>/data/dev` before the start.
9. **`docker/README.md`.** Copy the template `README.template.md`, which is next to this skill. Fill in the `<...>` markers (URL, ports, domains, secrets of `.env.prod`). Remove from the README what the project does not use, such as the certificate section when there is no HTTP server.
10. **Make it work**, in this order. Fix problems until everything passes:
- `docker compose -f compose.yaml -f compose.dev.yaml config` and the same with `-f compose.prod.yaml --env-file .env.prod` check the interpolation and show the names.
- The dev `up` of the README: everything is `healthy` and the app answers.
- Check hot reload and the owner of the folders (`../docker/references/development.md` and `../docker/references/hot-reload.md`).
- Check h2 and h3, if there is an HTTP server (`../docker/references/https.md`).
- The local prod test of the README, with `IMAGE_TAG=local`.
- Each command of `docker/README.md` runs as written.
11. **Report.** List the files, the commands to start dev and prod (the ones in `docker/README.md`), and the baseline of `../docker/references/measure.md` (build, up and size of the prod image).
## Out of scope
Architecture optimization and build time optimization belong to `docker:tune`. CI pipeline and registry belong to `docker:ci`, in a separate change. Orchestrator (Swarm, Kubernetes): only on request. The deploy sketch in the README is only a template.
Files in this package (2)
- README.template.md 3 KB
- SKILL.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · kamoca-labs/docker | 90 | MIT |
| verygoodopensource/vgv-wingspan | 100 | MIT |
| crisandrews/clawcode | 100 | MIT |
| digital-stoic-org/agent-skills | 100 | MIT |
| turalowski/agents | 100 | MIT |
| turalowski/agents | 100 | MIT |
| turalowski/agents | 100 | MIT |
| Borda/AI-Rig | 100 | Apache-2.0 |
| ninjanazal/team-chat | 100 | MIT |
Database snapshot: 13.11.2026 · package version d453a0cc5510 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100docker-patterns
Dockerfile best practices, multi-stage builds, docker-compose for dev/prod. Use when setting up containerization for a NestJS backend or Next.js frontend, or configuring a local dev environment with docker-compose. - 100dockly
Analyzes project dependencies to generate Dockerfile and docker-compose.yml. Use when the user asks to deploy, dockerize, or put the app on a server. - 100dockerize
Containerize an existing project with a production-ready Dockerfile, .dockerignore and docker-compose.yml, then build and run it to verify. Use when the user says "dockerize this", "add a Dockerfile", "run this in Docker", "containerize the app", or "docker-compose for local dev". - 100relay-docker
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this". - 100docker-packaging
This skill should be used when the user says \"create Dockerfile\", \"dockerize project\", \"Docker packaging\", \"container setup\", \"multi-stage build\", \"Docker Compose\", \"containerize application\", \"create docker-compose.yml\", \"create .dockerignore\", \"optimize… - 100trove-docker
Dockerfile and Docker Compose best practices. Auto-activates on Docker files. Use when: dockerfile; docker compose; containerize.