菜单
Add a new environment variable to the backend the right way — boot-time validation, .env.example documentation, and typed access. Use when introducing any new backend config/secret/flag.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-env-var |
| description | Add a new environment variable to the backend the right way — boot-time validation, .env.example documentation, and typed access. Use when introducing any new backend config/secret/flag. |
Backend env is validated at boot (fail-fast) in src/config/env.validation.ts.
A misconfigured/missing required var must crash startup, not fail silently later.
src/config/env.validation.ts on the
EnvironmentVariables class:
@IsString() (no @IsOptional). Add stronger checks where it
matters: @MinLength(32) for keys, @IsUrl(...), @IsNumber(), @IsEnum(...).@IsOptional() and a sensible default (= '...')..env.example with a comment and a working dev placeholder.
⚠️ If the var is required, the placeholder MUST satisfy validation so a fresh
cp .env.example .env boots (e.g. a ≥32-char string for a key). Mark clearly to
change it for prod.ConfigService.get<T>('NAME') (injected), or process.env.NAME
in non-DI spots (guards/services already do this) — handle the
not-configured case (fail-closed in production where it's a security control).EncryptionService). Ensure it's covered by .gitignore if it lands in a file.backend/AGENTS.md's "Required env" list if the var is required.backend/): bunx tsc -p tsconfig.build.json --noEmit.Mobile public config goes in app.config.ts / src/constants/config.ts via
EXPO_PUBLIC_* (never put secrets in the mobile bundle).
Scaffold a new mobile screen and/or API call in the Expo app following this project's conventions (design-system components, navigation, TanStack Query api/core, theme, i18n). Use when adding or extending a mobile screen or backend call.
Change the Prisma schema and create an incremental migration the standard Prisma way (migrate dev for local, migrate deploy for prod), then regenerate the client and seed. Use whenever editing backend/prisma/schema.prisma or adding/altering DB tables, columns, indexes, or enums.
Scaffold a new NestJS endpoint/module/route in the backend following this project's conventions (module + controller + service + dto + constants, auth/roles, pagination, prisma, tests). Use when adding or extending a backend API.
Audit the project against its production/deploy checklist — required secrets, migrations, store/push config, security toggles, and the verification gate. Use before a release, a deploy, or when asked if the app is production-ready.
Diagnose and fix this project's known environment, toolchain, build, and runtime traps (bun/node shell errors, ESLint version/commit failures, TS path/CSS errors, IAP/auth 500s, FCM iOS errors). Use when a command fails, a commit is blocked, or the app errors in a way that matches a known symptom.
Write unit tests following this repo's conventions for backend (NestJS, ts-jest, *.spec.ts) and mobile (jest-expo, *.test.ts, RNFB/native mocking). Use when adding test coverage for services, guards, pipes, hooks, stores, or utilities.