Menu
Keep environment variables and deploy-time settings inside a typed config boundary
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
Enforce six-layer forward-only imports: types -> config -> repositories -> services -> runtime -> ui
Write ADRs for harness boundaries, provider choices, dependency exceptions, and enforcement changes
Introduce the six-layer harness into an existing TypeScript project gradually
Fix six-layer harness violations reported by dependency-cruiser, ESLint, or review
Review a PR for six-layer harness, provider, ADR, and enforcement consistency
Keep auth, telemetry, flags, and external connectors behind provider interfaces
| name | config-boundary |
| description | Keep environment variables and deploy-time settings inside a typed config boundary |
| metadata | {"type":"Reference","origin":"harness-engineering/ch5","helpful":0,"harmful":0,"status":"active"} |
process.env only in the config layer.// NG: service reads process.env directly
const endpoint = process.env.BILLING_API_URL;
rg "process\\.env" src only hits config files