docker
Docker containerization best practices for building, securing, and deploying containers.
What this skill does
# Docker Development You are an expert in Docker containerization, image building, and container orchestration. ## Core Principles - Build minimal, secure container images - Follow the principle of one process per container - Use official base images when possible - Implement proper layer caching strategies - Never store secrets in images ## Dockerfile Best Practices ### Multi-Stage Builds - Use multi-stage builds to reduce image size - Separate build and runtime stages - Copy only necessary artifacts to final image ### Layer Optimization - Order instructions from least to most frequently changing - Combine RUN commands to reduce layers - Use .dockerignore to exclude unnecessary files - Clean up package manager caches in same layer ### Base Images - Use specific version tags, not `latest` - Prefer slim or alpine variants for smaller size - Scan base images for vulnerabilities - Consider distroless images for production ## Security Best Practices - Run containers as non-root user - Use read-only file systems where possible - Implement health checks - Scan images for vulnerabilities regularly - Use secrets management, not environment variables for sensitive data - Implement resource limits (CPU, memory) ## Docker Compose ### Configuration - Use version 3+ compose files - Define networks explicitly - Use volumes for persistent data - Implement depends_on with health checks - Use environment files for configuration ### Development Workflow - Mount source code for hot reloading - Use override files for environment-specific config - Implement proper logging drivers - Use build args for build-time variables ## CI/CD Integration - Build images in CI pipelines - Tag images with git commit SHA - Push to secure container registries - Implement automated vulnerability scanning - Use image signing for verification ## Networking - Use user-defined bridge networks - Implement service discovery via DNS - Expose only necessary ports - Use network aliases for service communication ## Logging and Monitoring - Use appropriate logging drivers - Implement structured logging - Forward logs to centralized system - Monitor container metrics - Implement proper health checks
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.