aif-dockerize

Generate multi-stage Dockerfiles, Compose configurations, and production security audits for projects.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-dockerize-1t1scool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-dockerize
Source: https://github.com/1t1sCooL/zazyvala-bot/tree/main/.cursor/skills/aif-dockerize
Command: npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-dockerize-1t1scool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up Docker for a project requires writing multi-stage Dockerfiles, dev and production Compose files, .dockerignore rules, and deploy scripts, then hardening everything against security checklists. This Skill automates that entire workflow by analyzing the project's language, framework, and infrastructure dependencies, then generating or auditing a complete Docker configuration. ## Core Features & Use Cases - Three operating modes: generate a full Docker setup from scratch, enhance an existing local setup with production configuration, or audit a complete setup against a security checklist. - Deep project analysis: detects language, framework, package manager, entry point, ports, and infrastructure services (PostgreSQL, Redis, RabbitMQ, reverse proxies) from project files and code. - Production hardening: generates compose.production.yml with read-only filesystems, dropped capabilities, resource limits, log rotation, healthchecks, and no exposed infrastructure ports, plus deploy, update, rollback, backup, and health-check scripts. - Use Case: You have a NestJS application with PostgreSQL and want to deploy it. Run the skill to get a multi-stage Dockerfile, dev Compose with hot reload, a hardened production Compose file, .dockerignore, .env.example, and ops scripts, followed by a scored security checklist. ## 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 scans your project files to detect the language, framework, package manager, and infrastructure dependencies, then creates a multi-stage Dockerfile, compose.yml, compose.override.yml for development, compose.production.yml, and .dockerignore.

How to audit a Dockerfile and Compose setup for production 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, dropped capabilities, resource limits, healthchecks, log rotation, and secrets handling, then reports results with fix options.

Does the Docker generator support NestJS, FastAPI, Laravel, and Go projects?

Yes. It detects frameworks from dependency files: NestJS, Next.js, Express, and Fastify for Node.js; FastAPI, Django, and Flask for Python; Laravel and Symfony for PHP; and Gin, Echo, Fiber, and Chi for Go, with matching base images and dev commands.

Should I use Angie or Nginx as a reverse proxy in Docker Compose?

The skill prefers Angie, a fully Nginx-compatible fork with dynamic upstream management and built-in Prometheus metrics. Nginx and Traefik are also supported, and you choose during the interactive setup step.

Why does the production Compose file expose no database ports?

Infrastructure services like PostgreSQL and Redis communicate over an internal Docker backend network in production, so no host ports are exposed. Only the reverse proxy or app binds ports 80 and 443, reducing the attack surface.

When should I avoid adding services like Redis or RabbitMQ to Compose?

Only add services your code actually imports or connects to. The skill's over-engineering checklist removes unused infrastructure, unnecessary reverse proxies for single-service apps, and deploy scripts when CI/CD already handles deployment.