メニュー
Keep apps/*/lib/startup/validation.ts push order aligned with apps/*/.env.example section order when practical. Use when adding env vars, startup validation entries, or editing validation.ts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | startup-validation-env-order |
| description | Keep apps/*/lib/startup/validation.ts push order aligned with apps/*/.env.example section order when practical. Use when adding env vars, startup validation entries, or editing validation.ts. |
| version | 1.0.0 |
When adding or reordering entries in:
apps/api/src/lib/startup/validation.tsapps/management-api/src/lib/startup/validation.tsespecially after adding vars to the matching apps/<app>/.env.example.
Keep validation results.push(...) order aligned with the authoritative env template
(apps/<app>/.env.example) when practical:
.env.example.validateAllEnvironmentVariables, not mixed into an earlier category block.ACCOUNT_SIGNUP_MODE
before conditional mailer checks) may be validated earlier than their env section.category, not file order;
alignment is for maintainer ergonomics when editing both files side by side.When adding an env var:
apps/<app>/.env.example — authoritative section + key orderapps/<app>/src/lib/startup/validation.ts — matching push order (same app)infra/config/env-templates/*.env.example when the var is shared across apps.cursor/rules/startup-validation-env-order.mdc)config/index.tsCanonical 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.