generating-docker-compose-files
Execute use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app".
What this skill does
# Generating Docker Compose Files ## Overview Generate production-ready `docker-compose.yml` files for multi-container applications. Define services, networks, volumes, health checks, resource limits, and environment-specific overrides for local development, testing, and single-host production deployments. ## Prerequisites - Docker Engine 20.10+ and Docker Compose v2 (`docker compose version`) - Application Dockerfiles for each service or pre-built images available - Understanding of service dependencies and inter-service communication ports - Environment variable values or `.env` files for configuration - Sufficient disk space and memory for all containers defined in the stack ## Instructions 1. Scan the project for existing Dockerfiles, `docker-compose*.yml` files, and application entry points 2. Identify all services that compose the application stack (web server, API, database, cache, message queue, worker) 3. Define each service with image or build context, port mappings, and environment variables 4. Configure service dependencies using `depends_on` with health check conditions to ensure proper startup order 5. Create named volumes for persistent data (database files, uploads, cache) and bind mounts for development hot-reload 6. Define custom bridge networks to isolate service groups (frontend, backend, data tier) 7. Add health checks for each service to enable dependency-aware startup and container orchestrator integration 8. Set resource limits (`deploy.resources.limits`) for CPU and memory to prevent a single container from exhausting the host 9. Create environment-specific override files: `docker-compose.override.yml` for development, `docker-compose.prod.yml` for production 10. Validate the configuration with `docker compose config` to check for syntax errors ## Output - `docker-compose.yml` with service definitions, networks, and volumes - Environment-specific override files (`docker-compose.override.yml`, `docker-compose.prod.yml`) - `.env` file template with documented variables - Dockerfiles for services that require custom builds - Helper scripts for common operations (`start.sh`, `stop.sh`, `logs.sh`) ## Error Handling | Error | Cause | Solution | |-------|-------|---------| | `port is already allocated` | Another container or host process using the same port | Change the host port mapping or stop the conflicting process | | `network not found` | Referenced network not defined in the compose file | Add the network under the top-level `networks:` key | | `service depends on undefined service` | Typo in `depends_on` or missing service definition | Verify service names match exactly between `depends_on` and service definitions | | `volume mount permission denied` | Host directory owned by different user than container process | Use `user:` directive in service or set proper ownership with an init script | | `OOM killed` | Container exceeded memory limit | Increase `deploy.resources.limits.memory` or optimize application memory usage | ## Examples - "Generate a docker-compose.yml for a Node.js API + PostgreSQL + Redis stack with health checks, named volumes, and a development override with hot-reload." - "Create a compose file for a WordPress site with MySQL, Nginx reverse proxy, and Certbot for automatic SSL certificate renewal." - "Build a docker-compose stack for a microservices app with 3 APIs, RabbitMQ message broker, and a shared Postgres database with isolated networks." ## Resources - Docker Compose specification: https://docs.docker.com/compose/compose-file/ - Docker Compose best practices: https://docs.docker.com/compose/production/ - Compose file versioning: https://docs.docker.com/compose/compose-file/compose-versioning/ - Multi-environment guide: https://docs.docker.com/compose/extends/
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.