メニュー
Prevents workspace package omissions in Docker images by verifying runtime-stage COPY coverage for every app dependency. Use when editing Dockerfiles, debugging ERR_MODULE_NOT_FOUND in containers, or changing workspace dependencies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Canonical linear DB migrations under infra/k8s/base/ops/source/database/linear-migrations, ops bundles, env keys, and runners. Use when adding or changing SQL migrations, K8s DB bootstrap, or scripts/database in this repo.
When an E2E test verifies a specific element, pass it to the capture helper so the step screenshot is taken with that element vertically centered.
Create and use Metaboost git worktrees in sibling directories named metaboost_<branch_slug> (underscores). Use when starting feature work, moving WIP off the main checkout, or opening the correct worktree path for a branch.
Distributed tracing and OTLP export patterns. Use when adding trace context, log correlation, or Observability env — after Metaboost adopts a shared observability package.
When you finish a plan file in active/, automatically move it to completed/. If it's the last plan in its set, move the whole set. Use when completing any plan under .llm/plans/active/.
User vocabulary abcmemory and abcremember — where Cursor guidance lives and how to persist new instructions. Use when the user says abcmemory or abcremember.
| name | docker-runtime-workspace-parity |
| description | Prevents workspace package omissions in Docker images by verifying runtime-stage COPY coverage for every app dependency. Use when editing Dockerfiles, debugging ERR_MODULE_NOT_FOUND in containers, or changing workspace dependencies. |
Use this skill when editing Metaboost Dockerfiles or workspace dependencies.
Builder stages can compile successfully while runtime stages fail if a workspace package is not copied into the final image.
Typical failures:
ERR_MODULE_NOT_FOUND@metaboost/orm at container startupWhen a Dockerfile uses selective COPY --from=builder (not full packages/):
@metaboost/* dependencies in the target app's package.json.COPY --from=builder .../package.json ...COPY --from=builder .../dist/ ...infra/docker/local/**)Metaboost local Dockerfiles generally COPY packages/ ./packages/ (whole tree). That still requires:
package.json workspaces includes the new package path.package-lock.json updated after dependency changes.npm run build:packages includes the new package in dependency-safe order — see build-order skill and .llm/context/architecture.md.If a Dockerfile does not copy all of packages/, apply the slim runtime checklist above.
Primary paths:
infra/docker/local/api/Dockerfileinfra/docker/local/management-api/Dockerfileinfra/docker/local/web/Dockerfileinfra/docker/local/management-web/DockerfileAlso apply to any new Metaboost Dockerfile or CI image that builds from this monorepo.
From monorepo root, after Dockerfile edits:
docker build -f infra/docker/local/api/Dockerfile -t metaboost-api:test .
Use the Dockerfile path for the app you changed.