env-setup-wizard — Claude Code skill: what it does, how to install
env-setup-wizard structures .env files, configures Zod schema validation, and prevents secret leaks into git repositories.
MIT 308 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a claude-codeWhat env-setup-wizard does
The skill organizes application environment configuration across development, staging, and production tiers. It scaffolds files like .env.example, creates .gitignore exception rules, and sets up centralized modules such as src/lib/env.ts for database strings and API credentials.
Rather than reading untyped values from process.env, it writes startup validation logic using Zod. If a critical variable is missing, the process terminates immediately with an error log. It also handles Next.js environments by separating server secrets from client-exposed variables prefixed with NEXT_PUBLIC_, or via @t3-oss/env-nextjs.
Because the validation code relies on Zod and TypeScript, projects need those dependencies installed before running the generated checks.
What it helps with
- Scaffold clean
.env.exampletemplates and.gitignorerules - Add runtime environment validation using Zod schemas
- Isolate server secrets from browser variables in Next.js
- Prevent broken deployments caused by missing configuration
Example prompts for the agent
- Set up environment variables and validation for a Next.js app with Postgres
- Generate an
.env.exampletemplate and a type-safesrc/lib/env.tsfile - Configure startup env validation with Zod and handle client-side variables
How to install env-setup-wizard
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a claude-code2Manually: put the files in place
~/.claude/skills/env-setup-wizard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/env-setup-wizard/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a codex2Manually: put the files in place
.agents/skills/env-setup-wizard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a cursor2Manually: put the files in place
.cursor/skills/env-setup-wizard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills env-setup-wizard2Manually: put the files in place
.github/skills/env-setup-wizard/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path env-setup-wizardManually: put the files in place
.devin/skills/env-setup-wizard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about env-setup-wizard
How do I install env-setup-wizard in Claude Code?
Run this command in your terminal: npx skills add OneWave-AI/claude-skills --skill env-setup-wizard -a claude-code.
What does env-setup-wizard do?
It outlines environment hierarchy, writes example configuration files, and generates schema validation code to catch missing variables at startup.
Does env-setup-wizard support Next.js?
Yes, it configures separate client and server schemas, using NEXT_PUBLIC_ prefixes or the @t3-oss/env-nextjs helper.
Source text
SKILL.md · MIT
---
name: env-setup-wizard
description: Set up environment variables, .env files, and configuration management. Use when configuring environment variables, creating .env files, or managing app configuration.
---
# Environment Setup Wizard
## Instructions
When setting up environment configuration:
1. **Identify required variables** for the project
2. **Create .env structure** with proper organization
3. **Set up type-safe access** to env vars
4. **Add validation** on startup
5. **Document all variables**
## File Structure
```
project/
├── .env # Local development (git-ignored)
├── .env.example # Template (committed to git)
├── .env.local # Local overrides (git-ignored)
├── .env.development # Development defaults
├── .env.production # Production defaults
└── src/
└── lib/
└── env.ts # Type-safe env access
```
## .env.example Template
```bash
# ===================
# Application
# ===================
NODE_ENV=development
APP_URL=http://localhost:3000
PORT=3000
# ===================
# Database
# ===================
DATABASE_URL=postgresql://user:password@localhost:5432/dbname
# ===================
# Authentication
# ===================
# Generate with: openssl rand -base64 32
JWT_SECRET=
NEXTAUTH_SECRET=
NEXTAUTH_URL=http://localhost:3000
# ===================
# Third-party APIs
# ===================
# Get from: https://stripe.com/dashboard
STRIPE_SECRET_KEY=
STRIPE_PUBLISHABLE_KEY=
STRIPE_WEBHOOK_SECRET=
# Get from: https://resend.com
RESEND_API_KEY=
# ===================
# Storage
# ===================
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_REGION=us-east-1
S3_BUCKET_NAME=
```
## Type-Safe Environment (Zod)
```typescript
// src/lib/env.ts
import { z } from 'zod';
const envSchema = z.object({
// App
NODE_ENV: z.enum(['development', 'production', 'test']).default('development'),
APP_URL: z.string().url(),
PORT: z.coerce.number().default(3000),
// Database
DATABASE_URL: z.string().min(1),
// Auth
JWT_SECRET: z.string().min(32),
NEXTAUTH_SECRET: z.string().min(32),
NEXTAUTH_URL: z.string().url(),
// APIs (optional in dev)
STRIPE_SECRET_KEY: z.string().optional(),
RESEND_API_KEY: z.string().optional(),
});
// Validate on import
const parsed = envSchema.safeParse(process.env);
if (!parsed.success) {
console.error('Invalid environment variables:');
console.error(parsed.error.flatten().fieldErrors);
process.exit(1);
}
export const env = parsed.data;
// Type export for use elsewhere
export type Env = z.infer<typeof envSchema>;
```
## Next.js Specific
```typescript
// src/lib/env.ts for Next.js
import { z } from 'zod';
// Server-side variables
const serverSchema = z.object({
DATABASE_URL: z.string(),
JWT_SECRET: z.string(),
});
// Client-side variables (must start with NEXT_PUBLIC_)
const clientSchema = z.object({
NEXT_PUBLIC_APP_URL: z.string().url(),
NEXT_PUBLIC_STRIPE_KEY: z.string(),
});
export const serverEnv = serverSchema.parse(process.env);
export const clientEnv = clientSchema.parse({
NEXT_PUBLIC_APP_URL: process.env.NEXT_PUBLIC_APP_URL,
NEXT_PUBLIC_STRIPE_KEY: process.env.NEXT_PUBLIC_STRIPE_KEY,
});
```
## T3 Env (Recommended for Next.js)
```typescript
// src/env.mjs
import { createEnv } from "@t3-oss/env-nextjs";
import { z } from "zod";
export const env = createEnv({
server: {
DATABASE_URL: z.string().url(),
NODE_ENV: z.enum(["development", "test", "production"]),
},
client: {
NEXT_PUBLIC_APP_URL: z.string().url(),
},
runtimeEnv: {
DATABASE_URL: process.env.DATABASE_URL,
NODE_ENV: process.env.NODE_ENV,
NEXT_PUBLIC_APP_URL: process.env.NEXT_PUBLIC_APP_URL,
},
});
```
## .gitignore
```gitignore
# Environment files
.env
.env.local
.env.*.local
# Keep example
!.env.example
```
## Security Best Practices
1. **Never commit secrets** to git
2. **Use different values** per environment
3. **Rotate secrets regularly**
4. **Use secret managers** in production (Vault, AWS Secrets Manager)
5. **Validate on startup** to fail fast
6. **Prefix client vars** (NEXT_PUBLIC_, VITE_, REACT_APP_)
© OneWave-AI · MIT · OneWave-AI/claude-skills