env-patterns

Environment/config conventions (env vars, defaults, validation, CI/local differences). Use when adding config or diagnosing env-related failures.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

This Claude skill facilitates the standardization and management of environment variables and configuration patterns across the software development lifecycle. It helps developers maintain consistency between local environments and CI/CD pipelines by providing guidance on defaults, validation rules, and environment-specific overrides, effectively reducing deployment failures and configuration drift.

Use Cases

  • Case 1: Diagnosing 'works on my machine' issues by identifying missing or mismatched environment variables between local development and CI/CD environments.
  • Case 2: Implementing robust configuration loading logic, including .env file management and validation schemas for new feature flags or API keys.
  • Case 3: Standardizing cloud provider configurations, such as AWS_REGION and AWS_PROFILE, to ensure seamless transitions between local testing and cloud-native deployments.
nameenv-patterns
descriptionEnvironment/config conventions (env vars, defaults, validation, CI/local differences). Use when adding config or diagnosing env-related failures.

Env Patterns

When to use

Use this when the task mentions:

  • environment variables, config loading, .env, defaults
  • “works locally but not in CI”
  • AWS env vars (AWS_REGION, AWS_PROFILE) or other runtime configuration

Canonical repo doc

Read your repo’s environment/config conventions doc (commonly docs/env-patterns.md).