ln-731-docker-generator
Generates Docker and docker-compose configuration for multi-container development
When & Why to Use This Skill
The ln-731-docker-generator is a high-performance Claude skill designed to automate the creation of production-ready Docker and docker-compose configurations. It streamlines the containerization process for multi-container applications by generating optimized Dockerfiles, orchestration scripts, and Nginx configurations. By adhering to security best practices—such as multi-stage builds, non-root user execution, and minimal base images—this tool ensures that your development and production environments are scalable, secure, and consistent across different tech stacks including React, .NET, and Python.
Use Cases
- Bootstrap a full-stack development environment: Automatically generate Docker and docker-compose files for a React frontend and .NET/Python backend to ensure seamless local orchestration.
- Optimize production deployments: Create multi-stage Docker builds that separate build dependencies from the runtime environment, significantly reducing image size and attack surface.
- Standardize DevOps workflows: Implement consistent security practices across projects, including non-root user configurations, health checks, and automated .dockerignore generation.
- Configure Nginx as a reverse proxy: Generate tailored Nginx configurations for Single Page Applications (SPA) to handle routing and API proxying within a containerized architecture.
| name | ln-731-docker-generator |
|---|---|
| description | Generates Docker and docker-compose configuration for multi-container development |
ln-731-docker-generator
Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-730-devops-setup
Generates production-ready Docker configuration for containerized development.
Purpose & Scope
Creates Docker infrastructure for local development and production:
- Does: Generate Dockerfiles, docker-compose, .dockerignore, nginx config
- Does NOT: Build images, start containers, manage deployments
Inputs
| Input | Source | Description |
|---|---|---|
| Stack Type | ln-730 coordinator | frontend, backend-dotnet, backend-python |
| Versions | Auto-detected | Node.js, .NET, Python versions |
| Project Name | Directory name | Used for container naming |
| Ports | Defaults or detected | Frontend: 3000, Backend: 5000/8000, DB: 5432 |
Outputs
| File | Purpose | Template |
|---|---|---|
Dockerfile.frontend |
Frontend build & serve | dockerfile_frontend.template |
Dockerfile.backend |
Backend build & run | dockerfile_backend_dotnet.template or dockerfile_backend_python.template |
docker-compose.yml |
Service orchestration | docker_compose.template |
.dockerignore |
Build context exclusions | dockerignore.template |
nginx.conf |
Frontend proxy config | nginx.template |
Workflow
Phase 1: Input Validation
Validate received configuration from coordinator:
- Check stack type is supported (frontend, backend-dotnet, backend-python)
- Verify versions are valid (Node 18+, .NET 8+, Python 3.10+)
- Confirm project directory exists
Output: Validated configuration or error
Phase 2: Template Selection
Select appropriate templates based on stack:
| Stack | Templates Used |
|---|---|
| Frontend only | dockerfile_frontend, nginx, dockerignore |
| Backend .NET | dockerfile_backend_dotnet, docker_compose, dockerignore |
| Backend Python | dockerfile_backend_python, docker_compose, dockerignore |
| Full stack .NET | All of the above (dotnet variant) |
| Full stack Python | All of the above (python variant) |
Phase 3: Variable Substitution
Replace template variables with detected values:
| Variable | Source | Example |
|---|---|---|
{{NODE_VERSION}} |
package.json engines or default | 22 |
{{DOTNET_VERSION}} |
*.csproj TargetFramework | 9.0 |
{{PYTHON_VERSION}} |
pyproject.toml or default | 3.12 |
{{PROJECT_NAME}} |
Directory name | my-app |
{{DLL_NAME}} |
*.csproj AssemblyName | MyApp.Api.dll |
{{FRONTEND_PORT}} |
Default or detected | 3000 |
{{BACKEND_PORT}} |
Stack-dependent | 5000 (.NET), 8000 (Python) |
{{BACKEND_HOST}} |
Service name | backend |
Phase 4: File Generation
Generate files from templates:
- Check if file already exists (warn before overwrite)
- Apply variable substitution
- Write file to appropriate location
- Validate syntax where possible
File Locations:
Dockerfile.frontend->src/frontend/DockerfileDockerfile.backend-> project rootdocker-compose.yml-> project root.dockerignore-> project rootnginx.conf->src/frontend/nginx.conf
Supported Stacks
Frontend: React/Vite + Nginx
Requirements:
- package.json with build script
- Vite or CRA configuration
Generated:
- Multi-stage Dockerfile (builder + nginx)
- Nginx config with SPA routing and API proxy
Backend: .NET 8/9
Requirements:
- *.sln file in root
- *.csproj with TargetFramework
Generated:
- Multi-stage Dockerfile (SDK build + ASP.NET runtime)
- Health check endpoint configuration
Backend: Python (FastAPI/Django)
Requirements:
- requirements.txt or pyproject.toml
Generated:
- Multi-stage Dockerfile (builder + slim runtime)
- uvicorn (FastAPI) or gunicorn (Django) entrypoint
Security Best Practices
All generated files follow these security guidelines:
| Practice | Implementation |
|---|---|
| Non-root user | Create and use appuser (UID 1001) |
| Minimal images | Alpine/slim variants |
| Multi-stage builds | Exclude build tools from runtime |
| No secrets | Use environment variables, not hardcoded |
| Health checks | Built-in HEALTHCHECK instructions |
| Specific versions | Pin base image versions |
Quality Criteria
Generated files must meet:
-
docker-compose configvalidates without errors - All base images use specific versions (not
latest) - Non-root user configured in all Dockerfiles
- Health checks present for all services
- .dockerignore excludes all sensitive files
- No hardcoded secrets or passwords
Critical Notes
- Version Detection: Use detected versions from coordinator, not hardcoded defaults.
- Idempotent: Check file existence before writing. Warn if overwriting.
- Template-based: All generation uses templates from references/. Do NOT hardcode file contents.
- Security First: Every generated file must follow security best practices.
Reference Files
| File | Purpose |
|---|---|
| dockerfile_frontend.template | React/Vite multi-stage Dockerfile |
| dockerfile_backend_dotnet.template | .NET multi-stage Dockerfile |
| dockerfile_backend_python.template | Python multi-stage Dockerfile |
| docker_compose.template | docker-compose.yml template |
| dockerignore.template | .dockerignore template |
| nginx.template | Nginx configuration |
Version: 1.1.0 Last Updated: 2026-01-10