> generating-docker-compose-files
This skill enables Claude to generate Docker Compose configurations for multi-container applications. It leverages best practices for production-ready deployments, including defining services, networks, volumes, health checks, and resource limits. Claude should use this skill when the user requests a Docker Compose file, specifies application architecture involving multiple containers, or mentions needs for container orchestration, environment variables, or persistent data management in a Docker
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/docker-compose-generator?format=md"Overview
This skill empowers Claude to create fully functional Docker Compose files, streamlining the deployment of complex applications. It automatically incorporates recommended configurations for service dependencies, data persistence, and resource optimization.
How It Works
- Receiving User Input: Claude interprets the user's request, identifying the application's architecture and dependencies.
- Generating Compose Configuration: Based on the interpreted request, Claude generates a
docker-compose.ymlfile defining services, networks, volumes, and other configurations. - Presenting the Configuration: Claude provides the generated
docker-compose.ymlfile to the user.
When to Use This Skill
This skill activates when you need to:
- Generate a Docker Compose file for a multi-container application.
- Define service dependencies and network configurations for a Docker environment.
- Manage persistent data using Docker volumes.
- Configure health checks and resource limits for Docker containers.
Examples
Example 1: Deploying a Full-Stack Application
User request: "Generate a docker-compose file for a full-stack application with a Node.js frontend, a Python backend, and a PostgreSQL database."
The skill will:
- Generate a
docker-compose.ymlfile defining three services:frontend,backend, anddatabase. - Configure network connections between the services and define volumes for persistent database storage.
Example 2: Adding Health Checks
User request: "Create a docker-compose file for a Redis server with a health check."
The skill will:
- Generate a
docker-compose.ymlfile defining a Redis service. - Add a health check configuration to the Redis service, ensuring the container restarts if it becomes unhealthy.
Best Practices
- Service Dependencies: Explicitly define dependencies between services using the
depends_ondirective. - Environment Variables: Utilize
.envfiles to manage environment variables and sensitive information. - Volume Naming: Use named volumes for data persistence and avoid relying on host paths.
Integration
This skill integrates with other development tools by providing a standardized Docker Compose configuration that can be used with Docker CLI, Docker Desktop, and other container management platforms.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".