What problem does it solve? Managing environment variables across development and production often leads to committed secrets, missing configuration at runtime, and untyped process.env access that fails silently. This Skill provides a structured approach to organizing .env files and validating configuration on startup. ## Core Features & Use Cases - Structured .env Templates: Generates organized .env.example files grouping application, database, authentication, API, and storage variables. - Type-Safe Validation: Implements Zod schemas and T3 Env patterns that validate environment variables at startup and fail fast with clear errors. - Framework-Specific Patterns: Covers Next.js server/client variable separation with NEXT_PUBLIC_ prefixes and proper .gitignore rules to prevent secret leaks. - Use Case: When bootstrapping a new Next.js app with Stripe and a Postgres database, use this Skill to generate the .env.example template, a validated env.ts module, and gitignore rules in one pass. ## Quick Start Set up environment variable configuration with Zod validation and a .env.example template for my Next.js project.
