Menu
Keep monorepo build order dependency-safe and keep build-order docs in sync when build orchestration changes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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 | build-order |
| description | Keep monorepo build order dependency-safe and keep build-order docs in sync when build orchestration changes. |
Use this skill when you change root build orchestration, workspace build sequencing, or CI/local validation flows that affect build execution order.
From repo root, build in this order:
npm run build:packages — @metaboost/helpers first, then parallel helper packages, then
orm / management-orm, then helpers-i18n (see root package.json build:packages script)npm run build:apps — api, management-api, web, sidecars, management-webFor local dev and CI, prefer build:packages then build:apps. Root npm run build runs
npm run build --workspaces --if-present; do not rely on it alone for a clean first-time build when
package dist/ outputs are missing.
Package outputs (dist/*.d.ts) are required by downstream workspace builds. If order is broken,
first-time builds can fail with TS2307 module-resolution errors.
When changing build order/process, update all relevant sources in the same PR:
package.json (build, build:packages, build:apps)package.json, CI workflows)build:packagesDatabase bootstrap artifacts: when linear migration SQL changes, regenerate baselines per linear-baseline-gz-sync (not part of npm build, but often touched in the same infra PR).
build:packages (or app-local build) first.