environment-files

name	environment-files
description	Rules for .env file handling, .env.example template format, and what's allowed vs forbidden. Use when working with environment variables, API keys, or configuration files.

Environment Files

This skill provides comprehensive guidance on handling environment files, including .env files, .env.example templates, and security best practices.

Overview

Environment files contain sensitive configuration data that must be handled carefully. This skill defines what's allowed and forbidden when working with environment variables.

Critical Rules

DO NOT MODIFY

CRITICAL FILES - DO NOT MODIFY WITHOUT EXPLICIT INSTRUCTION:

• .env files: Never commit or modify environment files (except .env.example templates)
• .env.local, .env.development, .env.production - All actual environment files
• git configuration files

Allowed Operations

✅ Create/Edit .env.example

ALLOWED:

• Create/edit .env.example - template showing required environment variables (no actual secrets)
• Format: KEY_NAME=example_value_here (with descriptive placeholder values)

Example .env.example:

DATABASE_URL=postgresql://user:password@localhost:5432/dbname
NEXT_PUBLIC_API_URL=http://localhost:3000/api
OPENAI_API_KEY=sk-your-api-key-here

✅ Template Format Guidelines

When creating .env.example files:

1. Use descriptive placeholders: