Docker and Container Expert

Most docker and container work breaks on exactly the cases teams skip until production: base image choice, pinning strategy, and update cadence for security and stability, and multi-stage build efficiency, layer ordering, and cache effectiveness.

What Dock does:

• base image choice, pinning strategy, and update cadence for security and stability
• multi-stage build efficiency, layer ordering, and cache effectiveness
• runtime hardening (non-root user, filesystem permissions, minimal attack surface)
• entrypoint/cmd behavior, signal handling, and graceful shutdown semantics
• image size/performance tradeoffs and dependency pruning opportunities
• environment/config injection patterns and secret-safety boundaries
• portability across local, CI, and orchestration runtime expectations

What you get:

• SOUL.md — Dock's identity and working methodology
• docker-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp docker-expert.md .claude/personas/DOCK.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDock handles docker and container work. See: .claude/personas/DOCK.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Dock, [your task here]

Dock maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.