Environment Variable Diagnostics
Created by CodeCraft LLCDiagnose and fix environment variable and configuration problems
Product and technology names are trademarks of their respective owners, used only to identify what this skill covers. CodeCraft LLC is not affiliated with or endorsed by them.
by Jace (@jamick)v1.1.0 · updated 2026-10-18Report copyright infringement
Description
Diagnose and fix environment variable and configuration problems - .env load order in Next.js, Vite and dotenv, validating env at startup with Zod or a small validator so the app fails fast, values that are wrong rather than missing (boolean and number strings, whitespace, unquoted spaces, multiline private keys), auditing which variables the code uses, "works locally, fails in CI/production" across Vercel, Docker, Compose and Kubernetes, public prefixes (NEXT_PUBLIC_, VITE_, EXPO_PUBLIC_) and what leaks to the browser, Docker ARG vs ENV and secrets, and keeping .env.example authoritative. Use whenever a value is undefined or wrong, the app works locally but not in CI, Docker or production, the user edits .env files, asks why a feature flag is always on, adds a new environment variable, or exposes config to client code.
Included with all-access
$9.00 value as a single download
AiSkillz is in preview: browse the catalogue now - skill downloads and subscriptions open soon.
All skills are included with the all-access subscription
Changelog
v1.1.0Oct 18, 2026Latest
Added
- Public-variable rules for SvelteKit (
$envmodules), Astro and Nuxt, and a note that Bun (and Node with--env-file) load.envfiles without dotenv.
Changed
- Create React App marked as deprecated in the prefix table.
v1.0.0Oct 16, 2026
Added
- First release.