菜单
Env file value formatting — double quotes for Node/Docker .env; unquoted values for K8s source/*.env. Use when adding or editing .env, .env.example, or env templates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | env-file-formatting |
| description | Env file value formatting — double quotes for Node/Docker .env; unquoted values for K8s source/*.env. Use when adding or editing .env, .env.example, or env templates. |
When adding or editing env var files. Which rules apply depends on the file path (see below).
Applies to app .env / .env.example, infra/config/env-templates/*.env.example,
infra/config/local/*.env, and dev/env-overrides/local/*.env.example.
API_PORT="3000", DATABASE_HOST="localhost").= (e.g. OPTIONAL_VAR=).See .cursor/rules/env-file-formatting.mdc for examples.
source/*.envApplies to infra/k8s/**/source/*.env (and GitOps overlay copies) consumed by configMapGenerator.
DB_PORT=5432, not DB_PORT="5432".KEY=.# line.Keep keys aligned with infra/config/env-templates/*.env.example. See also
infra/k8s/INFRA-K8S-BASE.md.
For K8s YAML manifest value types (string vs numeric OpenAPI fields), see k8s skill — not this skill.
NEXT_PUBLIC_*If a file defines both keys that are not NEXT_PUBLIC_* (e.g. API_PORT, READINESS_*,
NODE_ENV, RUNTIME_CONFIG_*) and any NEXT_PUBLIC_*:
NEXT_PUBLIC_* assignments first (group with section comments as needed).NEXT_PUBLIC_* keys.Files that are only NEXT_PUBLIC_* or only server keys need no extra ordering.
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.