docker-compose-patterns
Docker Compose Patterns
Overview
Use this skill to define reliable multi-service local stacks for development, debugging, and integration testing.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Dependency and startup patterns:
references/compose-dependency-guidance.md
Templates And Assets
- Compose stack baseline:
assets/compose-stack-template.yaml
- Operations runbook:
assets/compose-operations-runbook-template.md
Inputs To Gather
- Services and dependencies required for target workflows.
- Required startup order and readiness conditions.
- Shared volumes/networks and data persistence needs.
- Local resource constraints and isolation requirements.
Deliverables
- Compose service topology with explicit dependency rules.
- Health-check strategy and startup stabilization policy.
- Environment and secret handling policy for local use.
- Developer runbook for common stack operations.
Quick Example
- API depends on DB and cache with health-check gating.
- Use named network; avoid host network unless required.
- Use profiles to separate optional services (e.g., observability tools).
Quality Standard
- Dependency behavior is deterministic and health-driven.
- Service contracts (ports, env, volumes) are explicit.
- Local stack startup/shutdown is repeatable.
- Secret handling avoids committing sensitive defaults.
Workflow
- Map required services and dependency graph.
- Define compose services, networks, volumes, and env boundaries using
assets/compose-stack-template.yaml. - Add health checks and readiness-aware dependency rules.
- Validate full stack startup and critical workflows.
- Document operational commands and troubleshooting notes in
assets/compose-operations-runbook-template.md.
Failure Conditions
- Stop when service dependencies are implicit or race-prone.
- Stop when local stack requires unsafe credential handling.
- Escalate when resource contention prevents reliable local execution.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9