HomericIntelligence

Architecture Compose Resource Limit Env Substitution — DevOps skill for Claude Code

DevOps community

Planning pattern for exposing hard-coded docker-compose deploy.resources limits/reservations (cpus, memory) as overridable Compose ${VAR:-default} substitutions WITHOUT changing default behavior.

How to install Architecture Compose Resource Limit Env Substitution

Installs to ~/.claude/skills/homericintelligence-projectmnemosyne-architecture-compose-resource-limit-env-substitution/SKILL.md

Terminal

mkdir -p ~/.claude/skills/homericintelligence-projectmnemosyne-architecture-compose-resource-limit-env-substitution && curl -fsSL https://raw.githubusercontent.com/HomericIntelligence/ProjectMnemosyne/HEAD/skills/architecture-compose-resource-limit-env-substitution.md -o ~/.claude/skills/homericintelligence-projectmnemosyne-architecture-compose-resource-limit-env-substitution/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Architecture Compose Resource Limit Env Substitution does

name: architecture-compose-resource-limit-env-substitution license: BSD-3-Clause description: "Planning pattern for exposing hard-coded docker-compose deploy.resources limits/reservations (cpus, memory) as overridable Compose ${VAR:-default} substitutions WITHOUT changing default behavior. CRITICAL test-breakage trap: yaml.safe_load does NOT interpolate ${VAR:-default} — it returns the literal string, so any test/parser that does float(limits['cpus']) on the raw YAML scalar raises ValueError

Alternatives in DevOps

Mirrord — Run any process, on your machine or in an AI agent's environment, as if it were a pod in your Kubernetes clust 5.3k ★
Claude Code Sandbox — Run Claude Code safely in local Docker containers without having to approve every permission 301 ★
Deploy To Docker — Build Docker image and start/redeploy the MCP Task Orchestrator container, reusing the last-used config by def 205 ★