env-patterns
Environment/config conventions (env vars, defaults, validation, CI/local differences). Use when adding config or diagnosing env-related failures.
When & Why to Use This Skill
This Claude skill streamlines environment configuration management by enforcing consistent patterns for environment variables, defaults, and validation. It helps developers bridge the gap between local development and CI/CD pipelines, ensuring robust application behavior across different runtime environments and preventing configuration-related failures.
Use Cases
- Scenario 1: Adding new configuration variables to a project while ensuring proper validation and default values are set for different environments.
- Scenario 2: Diagnosing and resolving 'works on my machine' issues where code fails in CI/CD pipelines due to missing or misconfigured environment variables.
- Scenario 3: Implementing standardized AWS runtime configurations (like AWS_REGION or AWS_PROFILE) across multiple deployment stages.
- Scenario 4: Auditing existing .env files and configuration loading logic to align with repository-specific conventions and security best practices.
| name | env-patterns |
|---|---|
| description | Environment/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).