メニュー
Env vars with code fallbacks must show the default in .env.example and K8s env files. Use when adding or editing env vars that have fallback values in code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | env-defaults-match-code |
| description | Env vars with code fallbacks must show the default in .env.example and K8s env files. Use when adding or editing env vars that have fallback values in code. |
When adding or editing environment variables that have fallback defaults in code (e.g.
readOptionalPositiveExpirationEnv('MEMBERSHIP_FREE_TRIAL_EXPIRATION', 2678400) or helpers that
treat unset as a documented default).
Exception: App config/index.ts modules must not use || / ?? fallbacks — see
config-type-safety rule. This skill applies to documented helper defaults and template parity,
not to hiding missing required config.
Non-empty defaults: If code has a fallback value, the .env.example and K8s source/*.env
templates must include that default value — not an empty string unless unset is intentional.
DEFAULT_FREE_TRIAL_EXPIRATION / MEMBERSHIP_FREE_TRIAL_EXPIRATION="2678400" in
templates when helpers default to 31 days.process.env.FOO === 'true' (default false) →
.env.example should show FOO="false" when documenting the default.Empty is intentional: Only leave an env var empty (KEY=) when the "unset" state IS the
intended default (e.g. LOG_DIR= means console-only, optional mailer keys when signup mode
does not require mail).
Conflicts — fix the right side: When the code fallback differs from what's already consistently set in env files:
source/*.env).apps/*/.env.example and apps/*/sidecar/.env.exampleinfra/config/env-templates/*.env.exampleinfra/k8s/base/*/source/*.env filesdev/env-overrides/local/*.env.example (via home override stubs)*_EXPIRATION keysCanonical 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.