What problem does it solve? Scattered process.env reads across components and hooks make configuration untyped, unvalidated, and prone to silent production failures. This Skill enforces a single validated config module so missing or malformed variables fail the build at boot instead of degrading silently in production. ## Core Features & Use Cases - Typed config layer: Routes all environment variable reads through a Zod-validated module (config/env.ts or config/env/), with ESLint no-restricted-syntax banning direct process.env access everywhere else. - Boot-time validation: Schema parsing runs at module load, throwing with the variable name and reason so bad configuration becomes a deployment blocker, not a runtime condition. - Layered env files: Manages .env, .env.production, and .env.example together, including an env-sync check asserting key parity between .env and .env.example. - Use Case: When adding a new NEXT_PUBLIC_GRAPHQL_API_URL variable, declare it in .env.example, add a URL-validating schema entry, set values in the layered files, and read it only from the config module. ## Quick Start Add a new environment variable to this project following the typed config module pattern and update the schema and env example files.
