aif-dockerize

Generates multi-stage Dockerfiles, Compose files, and security audits from project analysis.

31|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/letuhao/lore-weave --skill aif-dockerize-letuhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-dockerize
Source: https://github.com/letuhao/lore-weave/tree/main/.cursor/skills/aif-dockerize
Command: npx skills add https://github.com/letuhao/lore-weave --skill aif-dockerize-letuhao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up Docker for a project requires deep knowledge of multi-stage builds, Compose networking, security hardening, and per-language conventions. This Skill analyzes your codebase and generates a complete, production-grade Docker configuration — or audits and fixes an existing one — without manual trial and error. ## Core Features & Use Cases - Three operating modes: generate a full Docker setup from scratch, enhance a local-only setup with production configuration, or audit an existing setup against a security checklist. - Deep project detection: identifies language, framework, package manager, entry point, ports, and infrastructure dependencies (PostgreSQL, Redis, RabbitMQ, reverse proxy) from project files. - Production hardening: generates compose.production.yml with read-only filesystems, dropped capabilities, non-root users, resource limits, log rotation, and internal networks. - Use Case: You have a Node.js API with PostgreSQL and Redis and need to deploy it. Run the skill to get a multi-stage Dockerfile, dev/prod Compose files, .dockerignore, .env.example, and deploy scripts — all pinned to verified image versions. ## Quick Start Ask the AI to dockerize this project and generate a production-ready Docker Compose setup with a security audit.

Frequently Asked Questions about aif-dockerize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dockerize an existing project with Docker Compose?

Run the skill in generate mode: it detects your language, framework, package manager, and infrastructure dependencies from project files, then creates a multi-stage Dockerfile, base and override Compose files, .dockerignore, and .env.example tailored to your stack.

How to audit an existing Dockerfile and Compose setup for security?

Use the --audit flag or run the skill when a full Docker setup already exists. It checks image pinning, non-root users, read-only filesystems, capability drops, resource limits, healthchecks, log rotation, and port exposure, then reports issues with severity levels and offers fixes.

Does it support my language or framework?

It detects Go, Node.js (Next.js, NestJS, Express, Fastify, Hono), Python (FastAPI, Django, Flask), PHP (Laravel, Symfony), and Rust. Base image versions are read from project files like go.mod, package.json engines, or pyproject.toml rather than hardcoded.

Can it add production hardening to my local Docker setup?

Yes, enhance mode handles projects that have local Docker files but no production configuration. It audits the existing files, then generates a hardened compose.production.yml with internal networks, no exposed infrastructure ports, and deploy scripts.

Why does the generated production Compose file expose no database ports?

Infrastructure services like PostgreSQL and Redis communicate over an internal Docker network and never bind host ports in production, reducing attack surface. Only the reverse proxy or app exposes ports 80/443; localhost binding is used when host access is truly required.