What problem does it solve? Hardcoded credentials and accidentally committed .env files are the root cause of most secret leaks. This Skill establishes a disciplined configuration pattern so no secret is ever hardcoded, committed, logged, or silently missing at runtime. ## Core Features & Use Cases - Environment-Driven Configuration: Reads every secret via os.getenv or process.env, with zero credential literals in code. - Placeholder-Only .env.example: Generates a committed template documenting every required variable without exposing real values, while keeping .env gitignored. - Fail-Fast Startup Validation: Checks all required variables at boot, lists missing ones in a clear error, and validates formats (e.g., Stripe keys starting with sk_). - Use Case: When preparing a repository for public sharing or onboarding a new developer, use this Skill to audit the codebase for hardcoded secrets, produce a complete .env.example, and add startup validation so misconfiguration fails loudly instead of leaking. ## Quick Start Set up secure environment variable configuration for my project with a placeholder .env.example, gitignored .env, and startup validation that fails fast on missing secrets.
