env-local
Generates .env.local file for local development environment variables. Contains developer-specific configuration like API URLs, ports, and feature flags. Gitignored for security.
When & Why to Use This Skill
This Claude skill automates the generation of `.env.local` files for local development environments. It streamlines the setup of developer-specific configurations—such as API URLs, ports, and feature flags—while ensuring security best practices by keeping sensitive credentials out of version control systems.
Use Cases
- Project Initialization: Quickly generate a standardized .env.local template when starting new web applications, specifically optimized for Vite-based projects.
- Local API Integration: Easily configure local backend endpoints and service ports to ensure the frontend communicates correctly with local microservices.
- Security Compliance: Automatically create gitignored environment files to prevent accidental exposure of sensitive API keys or secrets in public repositories.
- Feature Flag Testing: Define and manage local feature toggles and build modes (development, production, test) to test experimental code without affecting other environments.
| name | env-local |
|---|---|
| description | Generates .env.local file for local development environment variables. Contains developer-specific configuration like API URLs, ports, and feature flags. Gitignored for security. |
Environment Local Skill
Purpose
Generate .env.local file for local development environment configuration.
Output
Create the file: .env.local
Notes
.env.localis used for local development environment variables- This file should be in
.gitignore(never commit secrets) - Developers must replace
<>placeholders with actual values - Used by Vite to inject environment variables at build time
- All Vite env vars must be prefixed with
VITE_to be exposed to client code - NODE_ENV determines the build mode (development, production, test)